[jira] Resolved: (WW-2554) handleSpecialParameters in DefaultActionMapper not handling METHOD_PREFIX case

["Musachy Barroso (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/struts/browse/WW-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Musachy Barroso resolved WW-2554.
---------------------------------

    Resolution: Not A Problem

I agree with Don. Post a test case/example or a patch that makes it more clear, if you still think it is problem.

> handleSpecialParameters in DefaultActionMapper not handling METHOD_PREFIX case
> ------------------------------------------------------------------------------
>
>                 Key: WW-2554
>                 URL: https://issues.apache.org/struts/browse/WW-2554
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Core Actions
>    Affects Versions: 2.0.11
>            Reporter: Scott Stanlick
>             Fix For: 2.1.3
>
>
> When using the <s:submit method="pageThree" key="next"/> tag, the prefixTrie logic is not updating the "name" of the action mapping.  This is resulting in validators like Wizard-wizard-pageThree-validation.xml being skipped.   The ACTION_PREFIX case updates the name and requests work correctly through that code path.  I would guess the author of the METHOD_PREFIX had no way of determining what separated the action name from the wild character from the action mapping.

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