To me this is simple.. use one form and give is Session scope. Perfect for wizard stuff. You mentioned the sex screens are used to create a record in the DB, so one form to capture what you need makes sense.
Certainly I can see the reasoning behind that, but I would have to disagree. What if down the road I need to use one of those screens independant of that original flow? Isn't it just added complexity to have all the extra stuff in the ActionForm then?
A good example is the application I was talking about itself... The six screens are not simple in and of themselves, there is quite a bit of complexity to the ActionForms for each, in terms of how many fields there certainy. If I combined them all it would be a very unwieldly beast to maintain (I'd have to look, but I can imagine it being close to 2,000 line of code without much trouble, perhaps more).
In addition, how would you handle validation then? The validate() method is meant to apply to a single page (as is an ActionForm), but if you have the fields for six screens in one ActionForm, even if they function as one logical screen, wouldn't you be introducing branch logic to your validate() code to ensure you do the validations appropriate for the screen being submitted at the time since its now the only such method for six screens?
-- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
