[
https://issues.apache.org/struts/browse/WW-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Brown updated WW-2056:
--------------------------
Fix Version/s: (was: 2.1.2)
Future
I wonder if the issue is maybe in how the action chaining is happening. Why
not use an action redirect?
> ActionMapper: submit tag method attribute apply to all action(include action
> result)
> ------------------------------------------------------------------------------------
>
> Key: WW-2056
> URL: https://issues.apache.org/struts/browse/WW-2056
> Project: Struts 2
> Issue Type: Bug
> Components: Core Actions, Dispatch Filter, XML Configuration
> Affects Versions: 2.0.8
> Reporter: Cleven Lee
> Fix For: Future
>
>
> # In JSP:
> <s:submit value="Submit"/>
> <s:submit method="someMethod222" value="Submit 222"/>
> # In config file:
> <action name="someAction" class="SomeClass" method="someMethod">
> <result name="success">
> otherAction.action
> </result>
> </action>
> <action name="otherAction" class="SomeClass2" method="otherMethod">
> <result name="success">
> /someFile.jsp
> </result>
> </action>
> Then click "Submit 222", it will call SomeClass#someMethod222, then return to
> "otherAction.action" and call SomeClass2#someMethod222, not "otherMethod"
> method. Why not call method "otherMethod" I config?
> If config it like this:
> <action name="someAction" class="SomeClass" method="someMethod">
> <result name="success">
> otherAction!otherMethod.action
> </result>
> </action>
> It's will call SomeClass2#otherMethod. Is it a rule, or a bug? If it's a
> rule, it's so ugly, when I change the method name "otherMethod" to new name,
> I must any action result. Tks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
