The Jasper wrote: > Also, you might want to extend ValidatorActionForm instead of > ValidatorForm, but to tell the truth I'm not sure I really understand > the difference.
For future reference and completeness: You can specify validations based on either the form bean name or the action mapping path. ValidatorActionForm looks for validations based on the action path. This allows re-use of a form bean with potentially different validaton. One possible use is a "wizard" that uses one form bean to capture all information but does so across multiple web pages. If your validation is based on the action path you can validate only portions of the form bean for each page. ValidatorForm looks for validations based on the form bean name, meaning that you may only have one set of validations for that bean. FWIW I almost always use ValidatorActionForm (well, DynaValidatorActionForm) so I can reuse beans at will; if there's any advantage to using ValidatorForm I'm not sure what it is. (That's an implied question; are there any reasons?) Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
