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]
