Created: (WW-1741) make ExecuteAndWaitInterceptor token aware

make ExecuteAndWaitInterceptor token aware
------------------------------------------

                 Key: WW-1741
                 URL: https
://issues.apache.org/struts/browse/WW-1741
             Project: Struts 2
          Issue Type: Improvement
          Components: Interceptors
            Reporter: Thomas Micheline
            Priority: Minor


If the interceptor stack is configured as per the
documentaion and the ExecuteAndWaitInterceptor is placed
last, then the token interceptor will execute first,
validate the token, and then remove it from the session. 
The execute and wait interceptor could very easily replace
the token, if one exists in the parameters, in the session
before returning a wait result.

-- 
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-1741?page=com.at
lassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Micheline updated WW-1741:
---------------------------------

    Attachment: tokenizedEAW.patch

This patch implements the change described.

> make ExecuteAndWaitInterceptor token aware
> ------------------------------------------
>
>                 Key: WW-1741
>                 URL: https
://issues.apache.org/struts/browse/WW-1741
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Interceptors
>            Reporter: Thomas Micheline
>            Priority: Minor
>         Attachments: tokenizedEAW.patch
>
>
> If the interceptor stack is configured as per the
documentaion and the ExecuteAndWaitInterceptor is placed
last, then the token interceptor will execute first,
validate the token, and then remove it from the session. 
The execute and wait interceptor could very easily replace
the token, if one exists in the parameters, in the session
before returning a wait result.

-- 
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-1741?page=com.at
lassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ted Husted updated WW-1741:
---------------------------

    Fix Version/s: 2.1.0

> make ExecuteAndWaitInterceptor token aware
> ------------------------------------------
>
>                 Key: WW-1741
>                 URL: https
://issues.apache.org/struts/browse/WW-1741
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Interceptors
>            Reporter: Thomas Micheline
>            Priority: Minor
>             Fix For: 2.1.0
>
>         Attachments: tokenizedEAW.patch
>
>
> If the interceptor stack is configured as per the
documentaion and the ExecuteAndWaitInterceptor is placed
last, then the token interceptor will execute first,
validate the token, and then remove it from the session. 
The execute and wait interceptor could very easily replace
the token, if one exists in the parameters, in the session
before returning a wait result.

-- 
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-1741?page=com.at
lassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ted Husted reassigned WW-1741:
------------------------------

    Assignee: Ted Husted

> make ExecuteAndWaitInterceptor token aware
> ------------------------------------------
>
>                 Key: WW-1741
>                 URL: https
://issues.apache.org/struts/browse/WW-1741
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Core Interceptors
>            Reporter: Thomas Micheline
>            Assignee: Ted Husted
>            Priority: Minor
>             Fix For: 2.1.1
>
>         Attachments: tokenizedEAW.patch
>
>
> If the interceptor stack is configured as per the
documentaion and the ExecuteAndWaitInterceptor is placed
last, then the token interceptor will execute first,
validate the token, and then remove it from the session. 
The execute and wait interceptor could very easily replace
the token, if one exists in the parameters, in the session
before returning a wait result.

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