"Craig R. McClanahan" wrote:
> To handle lots of parameters to an Action, one very simple mechanism
> would be to interpret the single "parameter" included in an <action> as
> the name of a properties file resource containing your other configuration
> items. Otherwise, you have to go to the pain of extending ActionMapping
> to have some additional properties, and then using nested
> <set-property) elements to configure them.
This is what I really meant when I said multi-use: more than a single
parameter.
The properties resource file is an interesting suggesting, which
counting the posts on DEV, make for three
1) Handle it like a HTTP parameter --
parameter="parameter1¶meter2=value2"
2) Extend ActionMappings to make it a list of parameters: <parameter
name="param1" value="value1" /> <parameter name="param2" value="value2"
/>
3) Handle it like name of a properties file resource
-Ted.