Break in different classes is not the idea, in that way we need a class for 
each method or action. The solution is:

<result name="input">{1}.jsp</result>

In that way the method has the same name of the jsp, and the input is 
variable!! Works fine! 


Manuel Correa.


-----Original Message-----
From: Gary Affonso [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, November 06, 2007 7:58 PM
To: Struts Users Mailing List
Subject: Re: S2: input by method for validations

Maybe this is obvious, but why not just break this into two different 
action classes?  Then you get easy control of where you map the "INPUT" 
result code generated when the DefaultWorkflowInterceptor detects a 
validation error.

- Gary

Manuel Correa wrote:
> I found this:
> <interceptor-ref name="workflow">
>                       <param name="inputResultName" >inputA</param>
>                       </interceptor-ref>
> 
> That is the way that you can change the default input. 
> My question is:
> 
> I using wildcards for instance the methods... I can do this:
> 
> <interceptor-ref name="workflow">
>                       <param name="inputResultName" >input_{1}</param>    
> (This doesn't work)
>                       </interceptor-ref>
> 
> I need to find a way to define dynamically the input depends of the method 
> that is call.!! 
> Thanks 
> 
> Manuel Correa.
> 
> 
> -----Original Message-----
> From: Dave Newton [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, November 06, 2007 1:00 PM
> To: Struts Users Mailing List
> Subject: RE: S2: input by method for validations
> 
> You *might* be able to use an OGNL property to
> configure the name of the input result as an
> interceptor param; I don't know if they support
> parsing, though.
> 
> d.
> 
> --- Manuel Correa <[EMAIL PROTECTED]> wrote:
> 
>> The validations works fine. Sorry about the mistake.
>> The problem is the result: The input. When something
>> is wrong with the fields..by default the validation
>> stack forward to the INPUT, I need to define depends
>> of the method which is the input.
>>
>> Manuel Correa.
>>
>>
>> -----Original Message-----
>> From: F�tima Silveira [mailto:[EMAIL PROTECTED] 
>> Sent: Tuesday, November 06, 2007 12:20 PM
>> To: Struts Users Mailing List
>> Subject: Re: S2: input by method for validations
>>
>> the name of the XML must be like
>>
>> ClassName-actionAlias_methodName-validation.xml
>>
>> so you must rename your xml to
>>
>> Class-classAction_methodA-validation.xml
>>
>> Class-classAction_methodB-validation.xml
>>
>>
>> On 11/6/07, Manuel Correa <[EMAIL PROTECTED]>
>> wrote:
>>> I need to define a custom input for method in the
>> same action.
>>>
>>>
>>> For example, I have the "methodA"  that receive
>> the information from
>>> inputA.jsp
>>>
>>> I have "methodB" that receive from inputB.jsp
>>>
>>> I use the validation for each one:
>>>
>>>
>>>
>>> classAction_methodA-validation.xml
>>>
>>> classAction_methodB-validation.xml
>>>
>>>
>>>
>>> The problem occurs  when  the validations
>> fails(some input field is
>>> wrong) and need to redirect to the input. In this
>> case are two inputs in
>>> the same Action but in different methods... In
>> some way to say to the
>>> action the default input.
>>>
>>>
>>>
>>> Something like:
>>>
>>> <result name="inputA">inputA.jsp</result>
>>>
>>>
>>>
>>> <result name="inputB">inputB.jsp</result>
>>>
>>>
>>>
>>> <result name="input">inputDefault.jsp</result> 
>> (Other method by default
>>> use the input)
>>>
>>>
>>>
>>>
>>>
>>> But he validations understands to which input
>> goes.
>>>
>>>
>>> Manuel Correa.
>>>
>>>
>>>
>>>
>>
> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> [EMAIL PROTECTED]
>> For additional commands, e-mail:
>> [EMAIL PROTECTED]
>>
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


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


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

Reply via email to