I don't want to do much of anything in the action. Rather, I want the reading of the first form into FirstFormAction and the population of the second form handled by the framework which means that it has to be available to the Action. The best solution, I assume, would be to have an overloaded signature in the action execute(...) with (...ActionForm [] forms...) instead of (...ActionForm form....).
OK, I'm confused now. How will the framework populate the second form (this is the one intended to prepopulate fields on the destination page?) Did you just mean that you wanted it instantiated? Or are you looking for a more comprehensive service?
If you received an array of forms in the execute() method, how would you know which ones were input forms and which ones were intended for prepopulation for view support? I suppose maybe you could get a map of forms instead of an array. Perhaps even something like "mapping.findForm("formName")" along the lines of "mapping.findForward("path")".
Still, I'm not that keen on monkeying with the signature; no doubt because of my development history, I'd prefer to change to a single method which receives an ActionContext which can then be adjusted to have any values it needs without changing the Action API again.
It seems that one could implement this as an abstract base Action class which did the form instantiation/lookup in "execute(m,f,r,r)" and then called "execute(m,f[],r,r)".
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
