I'm obviously missing something. Am I understanding this scenario correctly:
I have 2 methods in my Action class: 'init' and 'save'. The 'init' method instantiates an instance variable 'myList', which is available to the jsp page thru a 'getList' method. The page is loaded and the 'myList' properties are displayed and edited. The user presses the 'save' button, and a new instance of the Action is class is created, so there is no longer a reference to the edited 'myList' object. If I were to implement 'ModelDriven' to push the 'myList' onto the stack, would this object persist through the Request/Response cycle. Would there be any benefit to that over storing it in the session? Thanks, Ray Clough Dave Newton-4 wrote: > > --- Ray Clough <[EMAIL PROTECTED]> wrote: >> Is the creation of a new instance the standard >> behavior - I can't believe it is, because that would > >> make the whole 'thread-safe' model in S2 pointless. > > That's *why* it's thread-safe. > > d. > > > > > ____________________________________________________________________________________ > No need to miss a message. Get email on-the-go > with Yahoo! Mail for Mobile. Get started. > http://mobile.yahoo.com/mail > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/%28S2%29-submit-question-tf3717366.html#a10403062 Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
