Craig, That's true, I could have subclassed DynaValidatorForm and modified the reset() method to accomodate my needs.
Originally, I had taken that route, but then found myself with many ActionForm subclasses to accomodate all sorts of scenarios - I had subclasses of DynaActionForm, DynaValidatorForm, and ActionForm, just to turn off reset(). I found that by centralizing the reset "switch" and being able to declare it in the struts-config.xml made my code and config files much cleaner, re-usable, and easier to maintain. I also figured that if the validate() hotspot could be turned on and off from the struts-config.xml, why not reset()? Jason Rosen -----Original Message----- From: Craig R. McClanahan [mailto:craigmcc@;apache.org] Sent: Monday, November 11, 2002 11:04 AM To: Struts Developers List Subject: RE: Unclear semantics on form use for "wizards" On Mon, 11 Nov 2002, Jason Rosen wrote: > Date: Mon, 11 Nov 2002 10:04:42 -0800 > From: Jason Rosen <[EMAIL PROTECTED]> > Reply-To: Struts Developers List <[EMAIL PROTECTED]> > To: Struts Developers List <[EMAIL PROTECTED]> > Subject: RE: Unclear semantics on form use for "wizards" > > Hi, > > I actually had a similar problem with wanting to use Session scoped > ActionForms and not having them reset every time they were recycled by > an Action. > An alternative strategy is to make the reset() method of your form beans smarter about which page of a multi-page wizard this submit is for (easy to determine because reset() has access to the request). Craig -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
