Instead of writing different action forms you can have different entries in your struts config with the same Object type (i.e action form ).In this was you can have different rule for each form using the validator framework. Does this sound feasible. Michael Lee <[EMAIL PROTECTED]> wrote:Along the same thread, we are having a validation design problem. We have broken most of our Action classes up into multiple classes. Before we had one and used the property in the action mapping. That makes the Action classes much more readable. Problem is, these action classes still just use one ActionForm. This ActionForm's validation method checks the parameter because the validation for each page is different. This is starting to get large and unwieldy. I don't want to have to create basically the same ActionForm for each Action class when they are all mostly the same. Question is, what is a clean way of breaking up all these validations? Should I continue to check the action parameter and validate against it within the same validation method for that one Action form? I was thinking of extending the UserForm (the ActionForm in question) and just implementing the validation method. This way I could also get rid of the parameter in the action mapping of the struts-config.xml. Thanks, Mike
----- Original Message ----- From: "Richards, Devin N (Devin)" To: "Struts Users Mailing List" Sent: Thursday, October 24, 2002 1:58 PM Subject: RE: Validator later rather than sooner? > Since the validator classes extend the standard struts classes, I would get everything working correctly and then add the validator in after. We did this and it worked well (except for the current bug of the validator not supporting multiple resource bundles.) > > -Devin > > > -----Original Message----- > From: Susan Bradeen [mailto:SusanB@;softlanding.com] > Sent: Thursday, October 24, 2002 1:50 PM > To: [EMAIL PROTECTED] > Subject: Validator later rather than sooner? > > > Is it general practice, or recommended, to develop a Struts application > using the Action/ActionForm classes first (getting everything working > properly) and later switch to the Validator classes, OR to use the > Validator classes (implementing validation) right from the beginning? > > I have done a little with form validation, but not enough to know if I > will get myself in trouble by waiting and "switching" class sets later on. > > Thanks, > Susan Bradeen > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > -- To unsubscribe, e-mail: For additional commands, e-mail: --------------------------------- Do you Yahoo!? Y! Web Hosting - Let the expert host your web site
