Darren, I use DynaValidatorActionForm and had to override the validate(). In the overriden method, I get the action path and append the operation value to it. This "primary key" uniquely identifies my validation routines.
For example: If the action mapping was /account/doSomething and the method was 'create' then the validation routines would be identified by /account/doSomething-create. So you end up with form attribute values in your validation.xml file like /account/doSomething-create, /account/doSomething-view, and /account/doSomething-update. HTH, robert > -----Original Message----- > From: Darren Hill [mailto:[EMAIL PROTECTED]] > Sent: Friday, September 27, 2002 10:42 AM > To: 'Struts Users Mailing List' > Subject: ValidatorForm > > > Question. > > I have a ValidatorForm form that works with a LookupDispatchAction. > > One of the the actions is 'view'. But this populates the form after > validation. > > The question is ... how can I selectively validate a ValiatorForm ( ie. > Don't validate for 'view', 'create', but validate for 'update', etc ) > > Darren > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
