I've done the same thing with handling logins, but I put a stack in the session that stores request tokens, so I can keep forwarding the user elsewhere and just keep popping the requests off the stack as form tasks are completed (essentially rollbacks)
-----Original Message-----
From: Tim Sawyer [mailto:[EMAIL PROTECTED]]
Sent: Sat 5/18/2002 1:08 PM
To: Struts Users Mailing List
Cc:
Subject: RE: Small Complaint - Struts Impl.
On Sat, 2002-05-18 at 16:52, Craig R. McClanahan wrote:
> It is the third rule that is the most likely cause for problems,
> especially if you are using a single form bean to capture the data from
> multiple pages (such as in a wizard dialog) -- which is about the only
> time that using form beans in session scope really makes any sense anyway.
I'm using form beans in session memory because if the user returns to a
page I still want the data they have already entered to be displayed
back to them, even though I have already successfully processed that
data already on their first run through.
Would you suggest a different approach?
Tim.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
winmail.dat
Description: application/ms-tnef
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
