Created: (WW-2302) Separate applying of parameters from the ActionMapping from the request pa

Separate applying of parameters from the ActionMapping from
the request parameters
------------------------------------------------------------
----------------------

                 Key: WW-2302
                 URL: https
://issues.apache.org/struts/browse/WW-2302
             Project: Struts 2
          Issue Type: Improvement
          Components: Core Interceptors
            Reporter: Don Brown
             Fix For: 2.1.1


Currently, the parameters from the ActionMapping class are
mixed in with the parameters from the request.  They should
be split out and processed separately by a different
interceptor.  This lets an action handle ActionMapping
parameters in a different step in the lifecycle than the
request parameters.  For example, in the rest plugin, you
want to get a hold of the resource id from the url and
process it before having the parameters from the request
applied to the action.

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

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

Don Brown resolved WW-2302.
---------------------------

    Resolution: Fixed
      Assignee: Don Brown

Added new ActionMappingParametersInterceptor and put it in
the default stacks.

> Separate applying of parameters from the ActionMapping
from the request parameters
>
------------------------------------------------------------
----------------------
>
>                 Key: WW-2302
>                 URL: https
://issues.apache.org/struts/browse/WW-2302
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Core Interceptors
>            Reporter: Don Brown
>            Assignee: Don Brown
>             Fix For: 2.1.1
>
>
> Currently, the parameters from the ActionMapping class
are mixed in with the parameters from the request.  They
should be split out and processed separately by a different
interceptor.  This lets an action handle ActionMapping
parameters in a different step in the lifecycle than the
request parameters.  For example, in the rest plugin, you
want to get a hold of the resource id from the url and
process it before having the parameters from the request
applied to the action.

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