So by copying properties into a session scoped object from a request based form should avoid a lot of these problems then (assuming you don't populate new windows from the session that is).
The properties from the request based form will overwrite those stored previously perhaps from a different window.
Cheers Mark
On 13 Feb 2004, at 17:41, Robert Nocera wrote:
Mark,
My interpretation of that comment was that if a user has two windows open
and are going back and forth between the windows, the system may use
information from one window to update the information in the session that
actually relates to the old window. This would be a pretty poor design, but
it's the only interpretation I can guess.
So the following could happen:
1. User chooses to edit order A.
2. Order A information is stored in the session and user is taken to an
order edit screen.
3. User chooses to edit order B in a new window.
4. Order B information is stored in the session and user is taken to an
order edit screen.
5. User goes back to edit screen for order A and adds an item.
6. Because the session has Order B info in it, the info is either added to
Order B (instead of the intended Order A)
Seems to me a pretty easy thing to check if the info they are updating relates to the info in the session, but that could be just me.
-Rob
-----Original Message----- From: Mark Lowe [mailto:[EMAIL PROTECTED] Sent: Friday, February 13, 2004 11:22 AM To: Struts Users Mailing List Subject: Re: [OT] - Request against Session
Am i to assume that there's no issue then ? or am i being too stupid to warrant a response?
--------------------------------------------------------------------- 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]
