Musachy,

In the bug report, under Test 1 instructions it's shows it working against
2.1.2  In the second set of instructions (accidentally also called Test 1)
it details how to make it not work by swapping over to 2.1.6.

Did you by any chance run this test case standalone, using the second set
of instructions?

-B



                                                                           
             Musachy Barroso                                               
             <[email protected]                                             
             m>                                                         To 
                                       Struts Users Mailing List           
             01/29/2009 02:37          <[email protected]>            
             PM                                                         cc 
                                                                           
                                                                   Subject 
             Please respond to         Re: [S2] possible bug in 2.1.6 w/   
               "Struts Users           action chaining                     
               Mailing List"                                               
             <[email protected]                                             
                  he.org>                                                  
                                                                           
                                                                           
                                                                           




Thanks for the testcase. I am looking at it, and there is a very
similar case in showcase, but it seems fine.

http://localhost:8080/struts2-showcase/actionchaining/actionChain1!input

the output is:

Action Chain 1 Property 1: Property Set In Action Chain 1
Action Chain 2 Property 1: Property Set in Action Chain 2
Action Chain 3 Property 1: Property set in Action Chain 3

Do you see any difference from your testcase (which I haven't run yet)

musachy

On Thu, Jan 29, 2009 at 5:10 PM,  <Becky.L.O'[email protected]> wrote:
> Thanks, bug WW-2970 was submitted along with a test case.
> -B
>
>
>
>
>             Musachy Barroso
>             <[email protected]
>             m>                                                         To
>                                       Struts Users Mailing List
>             01/28/2009 11:43          <[email protected]>
>             AM                                                         cc
>
>                                                                   Subject
>             Please respond to         Re: [S2] possible bug in 2.1.6 w/
>               "Struts Users           action chaining
>               Mailing List"
>             <[email protected]
>                  he.org>
>
>
>
>
>
>
>
> This is the first report I hear, open a jira ticket and describe a
> test case to replicate the problem.
>
> musachy
>
> On Wed, Jan 28, 2009 at 12:03 PM,  <Becky.L.O'[email protected]>
> wrote:
>> Hadn't heard back from anyone about this.  I'll go ahead and file a bug
>> report.
>> No one is using action chaining with 2.1.6?
>>
>> Thanks,
>> -B
>>
>>
>>
>>
>>             Becky.L.O'Sulliva
>>             [email protected]
>>
To
>>             01/27/2009 11:58          "Struts Users Mailing List"
>>             AM                        <[email protected]>
>>
cc
>>
>>             Please respond to
Subject
>>               "Struts Users           [S2] possible bug in 2.1.6 w/
>>               Mailing List"           action chaining
>>             <[email protected]
>>                  he.org>
>>
>>
>>
>>
>>
>>
>>
>>
>> Hi group,
>>
>> We're trying to upgrade from 2.1.2 to 2.1.6 and ran into an issue.
>>
>> We use action chaining because it suits a particular requirement we had
> for
>> this application.
>> However, after upgrading, we're seeing that the value stack isn't
holding
>> on to values set by actions further up in the chain.   Has anyone tested
>> 2.1.6 with the chain interceptor?
>>
>> Thanks,
>> -Becky
>>
>>
>>
>> ---------------------------------------------------------------------
>> This message, together with any attachments, is
>> intended only for the use of the individual or entity
>> to which it is addressed. It may contain information
>> that is confidential and prohibited from disclosure.
>> If you are not the intended recipient, you are hereby
>> notified that any dissemination or copying of this
>> message or any attachment is strictly prohibited. If
>> you have received this message in error, please notify
>> the original sender immediately by telephone or by
>> return e-mail and delete this message, along with any
>> attachments, from your computer. Thank you.
>>
>> ---------------------------------------------------------------------
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> This message, together with any attachments, is
>> intended only for the use of the individual or entity
>> to which it is addressed. It may contain information
>> that is confidential and prohibited from disclosure.
>> If you are not the intended recipient, you are hereby
>> notified that any dissemination or copying of this
>> message or any attachment is strictly prohibited. If
>> you have received this message in error, please notify
>> the original sender immediately by telephone or by
>> return e-mail and delete this message, along with any
>> attachments, from your computer. Thank you.
>>
>> ---------------------------------------------------------------------
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
>
>
> --
> "Hey you! Would you help me to carry the stone?" Pink Floyd
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
>
>
>
> ---------------------------------------------------------------------
> This message, together with any attachments, is
> intended only for the use of the individual or entity
> to which it is addressed. It may contain information
> that is confidential and prohibited from disclosure.
> If you are not the intended recipient, you are hereby
> notified that any dissemination or copying of this
> message or any attachment is strictly prohibited. If
> you have received this message in error, please notify
> the original sender immediately by telephone or by
> return e-mail and delete this message, along with any
> attachments, from your computer. Thank you.
>
> ---------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>



--
"Hey you! Would you help me to carry the stone?" Pink Floyd

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]





---------------------------------------------------------------------
This message, together with any attachments, is
intended only for the use of the individual or entity
to which it is addressed. It may contain information
that is confidential and prohibited from disclosure.
If you are not the intended recipient, you are hereby
notified that any dissemination or copying of this
message or any attachment is strictly prohibited. If
you have received this message in error, please notify
the original sender immediately by telephone or by
return e-mail and delete this message, along with any
attachments, from your computer. Thank you.

---------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to