You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Leonard Lee (JIRA)" <ji...@apache.org> on 2010/12/13 18:22:04 UTC

[jira] Commented: (WW-3488) ChainingInterceptor doesn't copy the value stack to the target action

    [ https://issues.apache.org/jira/browse/WW-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970902#action_12970902 ] 

Leonard Lee commented on WW-3488:
---------------------------------

Would fieldErrors also get copied when copyErrors is set to true? My initial guess is no, but I could be mistaken. If not, should they be? I was depending on the field errors to get copied to a chained result in 2.1.8.1.

> ChainingInterceptor doesn't copy the value stack to the target action
> ---------------------------------------------------------------------
>
>                 Key: WW-3488
>                 URL: https://issues.apache.org/jira/browse/WW-3488
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Core Interceptors
>    Affects Versions: 2.2.1
>            Reporter: Mika Laukka
>            Assignee: Lukasz Lenart
>             Fix For: 2.2.2
>
>         Attachments: WW-3488-1.patch, WW-3488.patch
>
>
> This can be easily reproduced by running the bundled struts2-showcase web application.
> http://localhost:8080/struts2-showcase-2.2.1/actionchaining/actionChain1!input.action
> results in this:
> Action Chain 1 Property 1:
> Action Chain 2 Property 1:
> Action Chain 3 Property 1: Property set in Action Chain 3
> So clearly the properties set in action 1 and action 2 are lost in the chaining process.
> For comparison, version 2.0.14 output
> http://localhost:8080/struts2-showcase-2.0.14/actionchaining/actionChain1!input.action
> results in this:
> 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 
> Which is the expected result. This bug may be related to fixing of WW-2869.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.