You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Erik Pilz (JIRA)" <ji...@apache.org> on 2007/01/03 23:23:16 UTC

[jira] Updated: (WW-1593) ExecuteAndWaitInterceptor no longer works after upgrading from WebWork 2.2.4

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

Erik Pilz updated WW-1593:
--------------------------

    Priority: Major  (was: Critical)

I accidentally set the status to Critical. I'll leave it up to whomever is assigned the bug to adjust the setting.

Cheers,
Erik

> ExecuteAndWaitInterceptor no longer works after upgrading from WebWork 2.2.4
> ----------------------------------------------------------------------------
>
>                 Key: WW-1593
>                 URL: https://issues.apache.org/struts/browse/WW-1593
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Interceptors
>    Affects Versions: 2.0.1, 2.0.2
>         Environment: Sun JDK 1.5; WinXP; WebLogic 9.2
>            Reporter: Erik Pilz
>
> After upgrading from WebWork 2.2.4 to Struts 2.0.2-SNAPSHOT the actions that use the ExecuteAndWaitInterceptor no longer work. Looking at the changes to the interceptor it appears that the changes to add the "executeAfterValidationPass" property are causing the problem.
> To support this feature a new local variable "secondTime", which defaults to true, was added to the doIntercept() method. Later in the code are various checks to determine what result should be returned. The following is a condensed version of the if-else:
>             if (!secondTime && bp != null && !bp.isDone()) {
>                 return WAIT;
>             } else if (!secondTime && bp != null && bp.isDone()) {
>                 return bp.getResult();
>             } else {
>                 return actionInvocation.invoke();
>             }
> Looking at the code I can't see how the "secondTime" variable can ever be set to false except on the first iteration or if you're using the "executeAfterValidationPass" property.
> The workaround for now is to use the ExecuteAndWaitInterceptor that ships with WebWork 2.2.4. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira