Note: Do not use String properties with buttons and test for the value that's set. This will break as soon as the value attribute of the HTML button changes! This is likely because the value attribute is used as the button text.

Dynamic Set of Buttons

Consider a web page showing a shopping cart or similiar tabular data. Often there is a button belonging to each row, in case of the shopping cart a delete button to remove the item from the cart. The number of buttons is dynamic and the id that couples the button to an item cannot go to the value attribute because all buttons should read "delete".

The solution is to name the buttons like delete[123], delete[594], delete[494] where 123, 594 and 494 are, for example, item ids.

When the button for the item with the property id == "27" is pressed, a parameter named delete[27] and value "delete" is set in your action. The trick is to declare your action's "delete" property as a java.util.Map. Then, a key will exist for the button that was pressed.

public void class UpdateCart implements Action {
// Must be initialized to be usable as a Struts 2 input parameter.
private Map delete = new HashMap();
/**
* This is somewhat counter intuitive. But a property like "delete[OS:27]"
* that is set to "delete" by Struts 2 will be interpreted by the underlying
* OGNL expression engine as "set the property 27 of the action's property
* "delete" to the value "delete". So we must provide a getter for this
* action. A setter is not needed.
*/
public Map getDelete() {
return delete;
}
public String execute() {
for (Iterator i = delete.keySet().iterator(); i.hasNext(); ) {
String id = (String) i.next();
...
// do what ever you want
...
}
...
}
}

In this case it would not be necessary to iterate the whole keySet because it contains only one key but the same code can be use to handle sets of checkboxes if this is prefered later: