I see your points but I disagree. I try to keep session use to an ABSOLUTE minimum, because each session is stored in server memory and with every current user filling out form there is a change, be it slight or not, that the server will slow down or crash. I know it might be less desireable from a maintenance perspective buy my time and effort in development is a lesser concern weighed against the performance of a productions system. I totally understand that this probably won't happen, but planning for the worst case is never a bad idea.
I don't use action forms because I dont like em. No real reason other than that. I think action forms don't provide any real benefit if you are proficient in html and want precise to the pixel control of style on the presentation layer. Just my personal preference. -B -----Original Message----- From: Rick Reumann [mailto:[EMAIL PROTECTED] Sent: Monday, April 04, 2005 11:35 AM To: Struts Users Mailing List Subject: Re: Multi Step Forms Brian McGovern wrote the following on 4/4/2005 10:16 AM: > Sounds good. I think I want to only have 1 write to the db at the > end of Action3, and im hoping to not use the session cause this app > is gonna have alot of users. By saving it on the page, are you > talkin about using hidden form fields across the 3 pages or can i set > the oject in action 1 so that it is visible in action 2? I'm thinkin > hidden form fields are the way to go here .. you agree? I'd have to say this seems like a really ugly solution and a maintenance nightmare. I still don't see why you can't use the Session to help out. That's what it's there for. If you are going to have that many users that you can't use the Session to store a bean for each user while they are logged on, than the application has some other serious problems. If you don't want to use an ActionForm (which I'm totally confused why you can't if you are using Struts?) then just have each submission to each Action store the results in a bean that you keep in the Session. When you are all done (on the last step) persist this bean to the DB. So no, I don't agree hidden form fields are the answer. It's an icredible pain to maintain those hidden fields when requirements change, plus on each step you are going to put them all back into scope each time? Another maintenance nightmare. I see the above scenario as a perfectly acceptable use for Session scope. -- Rick --------------------------------------------------------------------- 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]
