I'm not sure about the answer to the second part of your question, but I'm about 99.99% sure you can still use it (anyone else verify?)
Frank
From: "Kunal H. Parikh" <[EMAIL PROTECTED]> Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]> Subject: RE: Single ActionForm accross multiple Actions Date: Wed, 9 Jun 2004 10:34:27 +1000
Great ...... thanks for all the responses...
I think I will go with the ActionForm stored in session-scope.
Just wanting to confirm, that I will need to perform the following code changes:
================== public ActionForward execute( ActionMapping actionMapping, ActionForm actionForm, HttpServletRequest httpServletRequest, HttpServletResponse httpServletResponse ) throws Exception { actionForm = httpServletRequest.getSession().getAttribute("myForm"); // ... // normal code follows!!! } ==================
Also, would I be correct in saying that I will be unable to use the ValidatorActionForm.
TIA,
Kunal
-----Original Message----- From: Frank Zammetti [mailto:[EMAIL PROTECTED] Sent: Tuesday, 8 June 2004 23:21 To: [EMAIL PROTECTED] Subject: RE: Single ActionForm accross multiple Actions
This is more or less what a session-scope ActionForm is for. As long as the
ActionForm class contains all the properties and methods for all the screen it will service, just putting it in session I think is your best bet. As someone else said, hidden form fields are your other choice. Actually, you could also store the data temporarily to a database, but if you would even consider that, session is really the right answer.
Frank
>From: "Kunal H. Parikh" <[EMAIL PROTECTED]> >Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> >To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]> >Subject: Single ActionForm accross multiple Actions >Date: Tue, 8 Jun 2004 12:08:25 +1000 > >Hi All! > >I want to maintain a single ActionForm across multiple Actions. > >I want to get the info from the user in a step-by-step manner, but only >wanna talk to the SessionBean at the end when they hit "confirm". > >The alternative that I can think of is writing a JavaBean with all the >properties, and pass the JavaBean around as a session attribute. > >Any one have a better solution ? > > >TIA, > >Kunal > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] >
_________________________________________________________________ Watch the online reality show Mixed Messages with a friend and enter to win a trip to NY http://www.msnmessenger-download.click-url.com/go/onm00200497ave/direct/01/
--------------------------------------------------------------------- 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]
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar – get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]