The validation interceptor will look for, and call, validate${methodName}
(and validateDo${methodName}).

d.

--- Martin Braure de Calignon <[EMAIL PROTECTED]> wrote:

> 
> Le vendredi 11 janvier 2008 à 09:15 -0500, Ted Husted a écrit :
> > On Jan 11, 2008 8:10 AM, Martin Braure de Calignon <[EMAIL PROTECTED]>
> wrote:
> > > Of course yes :-). But I need a validate() per method.
> > 
> > I haven't used it myself, but the syntax validate-action is suppose to
> > work, in the same way that it works for the validation framework.
> 
> I don't think so. You see, with per alias or per method validation, you
> can have multiple xml files for the same action with the filename
> format : ActionName-alias-validation.xml
> 
> e.g.: 
> if I have defined my action like this :
> <action name="CycleManagement!*" class="...[a class]" method="{1}">
>         <result name="A">View1.jsp</result>
>         <result name="B">View2.jsp</result>
>         <result name="C">View3.jsp</result>
> </action>
> 
> I can per alias validation. As I'm using wildcards, it is as if I
> defined CycleManagement!A action and CycleManagement!B action ...
> 
> So I can have :
> CycleManagement-CycleManagement!A-validation.xml
> CycleManagement-CycleManagement!B-validation.xml
> CycleManagement-CycleManagement!C-validation.xml
> 
> I don't see how implementing Validatable allow me such a thing. I will
> only have one Validate() method (without parameter) for my action class.
> 
> No ? Am I missing something ?
> 
> Cheers,
> 
> -- 
> Martin Braure de Calignon
> 


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

Reply via email to