Sorry. No I meant ValidatorActionForm................didn't realize that you were on 1.0.2. Forget what I said. It applies to 1.1 using the Validator.
What about doing your validation in the Action rather than the forms validate method? You could continue to use a common form (I'm guessing that you mean a common form used by a number of different actions, and NOT that there is just one form for the entire application). If I understand you correctly you are saying that the validation is dependant on the action (as I thought earlier). In that case the action would know what validation needs to be performed? You could even implement a number of different validation methods on the form, and the actions would call the appropriate validation method. Does this make more sense? Dave Derry ----- Original Message ----- From: "Michael Lee" <[EMAIL PROTECTED]> > If by ValidatorActionForm you mean ValidatingActionForm then I can't > (shouldn't). It recommends what I suggested as a possible solution in the > original post. That is, overriding the UserForm and using that form for the > appropriate action mapping in the struts-config.xml. I would be overriding > the validate() of UserForm which is overriding validate() of ActionForm. I'm > using struts 1.0.2 btw. > > Javadocs for ValidatingActionForm > "Deprecated. Application ActionForm beans should now extend ActionForm > directly, and override the validate() method if they wish to provide such > services" > thanks, > Mike > > ----- Original Message ----- > From: "Dave Derry" <[EMAIL PROTECTED]> > > > You can also validate based on the action rather than the form. Just use > the > > action type rather than the form name, and be sure to extend > > ValidatorActionForm rather than ValidatorForm. > > > > Dave Derry > > > > ----- Original Message ----- > > From: "bachan s" <[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
