Take a look at Action mapping wildcards. This could even help maintain sanity since you'll know what bean a certain action call will be expecting.
http://struts.apache.org/struts-action/userGuide/building_controller.html#action_mapping_wildcards Btw, questions like these should go to the user list. Hubert On 12/14/05, Stas Ostapenko <[EMAIL PROTECTED]> wrote: > Hi dev@struts.apache.org ! > > I'm interested in such feture. Is it possible to have one action to > handle different beans which can be changed at runtime ? For example I > have such action in struts-config.xml > <action > path="/AddDomainActionArea" > type="AddDomainAction" > name="domainForm" > input="/vm/DomainActionAdd.vm" > validate="true" > scope="request"> > <forward name="error_adding" path="/vm/DomainActionAdd.vm"/> > <forward name="added" path="/vm/DomainActionAddOK.vm"/> > </action> > It's ok when I have one object - Domain. But when we have 50 different > objects it's become a problem. Can parameters of action be changed at > runtime ? How it could be implemented. > Any suggestions are welcome. > > Thanks ! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
