[WW-2795] NoParameters blocks action tag params instead of request params

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Not A Problem
• Affects Version/s: 2.1.2
• Fix Version/s: 2.1.3
• Component/s: Core Interceptors
• Assignee: Unassigned
• Reporter: Raphael Kirchner
• Created: 01/Sep/08 14:15
• Updated: 28/Oct/12 22:11
• Resolved: 09/Dec/08 18:45

Description

According to JavaDoc, org.apache.struts2.interceptor.NoParameters should be "should be implemented by actions that do not want any parameters set on them automatically. This may be useful if one is using the action tag and want to supply the parameters to the action manually using the param tag."

Actually something like the opposite happens: The action tag param gets blocked and the request param is used instead

Example:

<@s.action name="Foo" executeResult="true" ignoreContextParams="true" >
<@s.param name="input">embedded</@>
</@s.action>

With Foo implementing NoParams,
1) Foo.action results in Foo.input == NULL
2) Foo.action?input=test results in Foo.input == "test"
Where it should be "embedded" in both cases.

<@s.action name="Foo" executeResult="true" ignoreContextParams="true" >
</@s.action>

With Foo implementing NoParams,
1) Foo.action results in Foo.input == NULL
2) Foo.action?input?test results in Foo.input == "test"
Where it should be NULL in both cases,