Oh, and I'm still open to making it possible to centralize validations without having to inherit them... Maybe an <include> element in the validation files like we have in xwork.xml? Then you could manage validations all in your XML files without needing a second place to look for what might have been defined for other sources of validation.
> -----Original Message----- > From: Francisco Hernandez [mailto:[EMAIL PROTECTED] > Sent: Friday, September 05, 2003 5:41 AM > To: [EMAIL PROTECTED] > Subject: [OS-webwork] using one validator on several different actions > > > I've been using the validator in webwork and have found myself > duplicating a few of the validations throughout the app, is > there anyway > I can apply validations to multiple actions or objects? > > for example I have a creation form to create a Car, and then I have > another to Edit and Update the Car, how could I create just one > validation file that will validate that Car? > > right now I've got 2 validation files, CreateCarAction-validation.xml > and UpdateCarAction-validation.xml and both are identical. > > im thinking maybe a way to specify what validation files to > use in the > action mapping? what do you guys think > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
