I simply configured my default set of interceptors as follows:
execute
execute
This makes sure that the validation doesn't occur when the action is initially
fired. You can add more methods to the list if you'd like to.
Ses
I use to have a loadAction for each page and the real action to post to...
Maybe I didn't catch the problem, do you use that scheme?
On 8/13/07, Session A Mwamufiya <[EMAIL PROTECTED]> wrote:
>
> Hi, I have an action that is validateable and uses the validate method to
> ensure that an element is
s Users Mailing List"
>
>
> A user@struts.apache.org cc
>
> Objet Preventing validation when form is first displayed
>
>
>
>
>
>
> Hi, I have an action that is validateable and uses the validate method to
> ensure that an element isn't added
So add the name of your first method in the excludeMethods, and the
validation will not occures.
"Session A Mwamufiya" <[EMAIL PROTECTED]>
13/08/2007 08:58
Veuillez répondre à
"Struts Users Mailing List"
A
user@struts.apache.org
cc
Objet
Preventing validation wh
Hi, I have an action that is validateable and uses the validate method to
ensure that an element isn't added to the database if it already exists in
there. Unfortunately, the validation occurs as soon as my form is launched. I
tried to follow the approach from the helloworld example to not hav
5 matches
Mail list logo