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]



Reply via email to