There are probably more ways, too. Depending on your design, I'd recommend Mark's suggestion. Validation in the Action makes sense particularly when using a variant of DispatchAction, wherein there will be many methods for different submissions, only some of which require validation, and perhaps differing validation.
m --- "Jens v.P." <[EMAIL PROTECTED]> wrote: > Hi, > > this question was asked several times before, I also > asked this > questions a week ago. Just have a look at the > mailing list archive. > > There are two approaches: > > 1) Two actions: "ViewFormFirstTimeAction" with > validate="false" in the > struts-config.xml, and ViewFormAction with > validate="true" > > 2) Create your own form class (as a subclass of a > validator form > class). Check whether the submit-value is present in > the quest and, if > not, skip super class validation, otherwise call > super class validation > function. Caution: You have to pay attention that in > the first case > your form is not skipped (no error occured and the > "success" page is > forwarded) - you maybe have to add a "firsttime" > forward or something > like this. > > Jens > > BTW: Oh - this question is also listed in the FAQ... > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
