as far as I am concerned, there is nothing wrong with having two action mappings. It is alot easier than coding something in the form class. I have heard of projects with many hundreds of action mappings, with no adverse impact on the project.

Wendy Smoak wrote:
Sashi wrote:

I do not want to validate when page loads, so how can I avoid it unless I

give


validate=false in the action mapping?


Override the validate method in your Form bean, and only call
super.validate() when appropriate.  How to decide that is up to you.  I use
a LookupDispatchAction, so I check for the userAction request parameter
being "Finish" which tells me the user is, well, Finished!

But you can place a hidden field on the form and check for that, or check
that the request has been POSTed to you which will (usually) indicate that
the form has been submitted.

Even with Dynamic Forms, I still have Java classes for each Form because I
need to control the validate and reset behavior.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to