[
https://issues.apache.org/struts/browse/WW-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Musachy Barroso resolved WW-2970.
---------------------------------
Resolution: Won't Fix
ok, this became the side effect of something else which I am not sure what it
was. Here is the problem:
When StaticParamsInterceptor runs on action1 then the static param is added to
the request param list, when chaining happens all fields are copied from
action1 to action2, and the field is set as expected, but when the params
interceptor runs on action2, then it "sees" the static param as a request param
because the StaticParamsInterceptor added it to the request params, and then it
sets the field in action2 to the static value.
Take a look at :
http://jira.opensymphony.com/browse/XW-709
The solution is to configure your "staticParams" interceptor and set the
"merge" attribute to false.
> Param set on chained action is re-set on all actions in chain
> -------------------------------------------------------------
>
> Key: WW-2970
> URL: https://issues.apache.org/struts/browse/WW-2970
> Project: Struts 2
> Issue Type: Bug
> Components: Core Interceptors
> Affects Versions: 2.1.6
> Environment: Windows XP SP2. WebLogic Server 10.0 MP1. Java
> HotSpot(TM) Server VM Version 1.5.0_11-b03
> Reporter: David
> Fix For: 2.2.0
>
> Attachments: chainapp.zip
>
>
> If a param is set on an action in a chain through struts.xml, it will be set
> on all subsequent actions in the chain, thus overwriting any values that may
> have been set by the actions themselves.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
