Given your scenario, it sounds like a good candidate for a session scoped form.
I agree with what Mark Lowe said - usually/often "...theres no more work invloved scoping to request" - thats been the case for my app. I would also do what you said in a previous post - which is "clean up" the session stuff when they navigate away to another part of the app. I'm in the "do it in request unless you have good reason(s) to use the session" camp - rather than the "anti-session" camp as it may have appeared in previous threads. Niall ----- Original Message ----- From: "Paul McCulloch" <[EMAIL PROTECTED]> To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]> Sent: Wednesday, February 25, 2004 4:13 PM Subject: RE: need help converting from session to request scope > My application has an Asset search form. The user can enter many criteria to > search on. > > Most of these criteria themselves are looked up from the database (e.g the > Person associated with the Asset search). When the user selects a search > criteria (e.g. the Person) I store the DTO for that person on my search > form. The view element displays details about that Person on the search form > until the search form is cleared. > > Many requests will be made to find the criteria before the Asset search > itself is performed. > > To do this using a request scope form would require that I transfer all of > the details I want to display about that person in hidden inputs on the > form. If the details I want to display about a Person change then I'd also > need to change the hidden fields. In addition once I ship the application to > my customers they may have their own JSP developer show extra prpoerties of > the selected Person. > > So, that's my justification for using session scoped form beans. Any > comments gratefully recieved. > > Paul --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
