While I agree that there is nothing wrong with calling validate()
yourself; if you are using 1.2 you might want to look into the
MappingDispatchAction -- it was designed to allow for one Action that
supports multiple action configurations -- even with different forms, etc.
Bryce Fischer wrote:
Rick Reumann wrote:
Vic wrote:
I allways say validate = false in mapping, and then manualy call it.
Would that help?
I do the same. Validating manually also gives you the nice advantage
of being able to set up any lists or other objects you need in request
scope if valdiation fails. Bryce, an ex
Vic wrote:
I allways say validate = false in mapping, and then manualy call it.
Would that help?
I do the same. Validating manually also gives you the nice advantage of
being able to set up any lists or other objects you need in request
scope if valdiation fails. Bryce, an example of it might loo
Vic wrote:
I allways say validate = false in mapping, and then manualy call it.
Would that help?
Thanks for your quick response Vic. Do you mean manually calling it in
the DispatchAction class (I think that's what you mean, but I didn't
want to assume)?
Bryce Fischer wrote:
I'm having a problem
49 PM
To: [EMAIL PROTECTED]
Subject: Re: ValidatorForm issue
I allways say validate = false in mapping, and then manualy call it.
Would that help?
.V
Bryce Fischer wrote:
> I'm having a problem with a ValidatorForm and validation. The first time
> I try to access the action below, I
I allways say validate = false in mapping, and then manualy call it.
Would that help?
.V
Bryce Fischer wrote:
I'm having a problem with a ValidatorForm and validation. The first time
I try to access the action below, I get a validation error. The form
never gets the opportunity to be filled in by
6 matches
Mail list logo
