Ahh. For situations where you have something like pageA ====> ProcessActionA ====> pageB ===> ProcessActionB
where pageA and pageB need 2 different forms. Yes. You would have to "insert" a SetupActionB in the chain which results in: pageA ====> ProcessActionA ====> SetupActionB ===> pageB ===> ProcessActionB Yes, SetupActionB would have to know how to extract formA data from the request and populate formB. But this sounds like a wizard style process where it might be better to use a single form for the entire process. I think this problem/solution has been hashed out on this list many times and the solution is subject to the complexity of the process. This pattern just happens to work for me and keeps things clean and separate. robert > -----Original Message----- > From: Joe Germuska [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 18, 2003 4:00 PM > To: Struts Users Mailing List > Subject: RE: [repost] Special view information -> ActionForm or request? > > > >I have a dynamic form defined in my struts config file and > >mapped to both SetupAction and ProcessAction. I don't have > >to manually create the form because Struts does this for me. > >Its actually very simple: > >... > >How is that clumsy? Am I missing something? > > What if the dispatch to the page preceding "ProcessAction" depends on > the submission of some form other than the one you require to handle > "SetupAction." It seems that your solution only works if you don't > need an ActionForm in SetupAction for anything except preparing the > view. > > Joe > > > -- > -- > Joe Germuska > [EMAIL PROTECTED] > http://blog.germuska.com > "If nature worked that way, the universe would crash all the time." > --Jaron Lanier > > --------------------------------------------------------------------- > 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]
