Mailing-List: contact issues-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@struts.apache.org
Date: Mon, 6 Apr 2015 20:17:13 +0000 (UTC)
From: "David Williams (JIRA)" <jira@apache.org>
To: issues@struts.apache.org
Message-ID: <JIRA.12761845.1418673181000.6878.1428351433183@Atlassian.JIRA>
In-Reply-To: <JIRA.12761845.1418673181000@Atlassian.JIRA>
References: <JIRA.12761845.1418673181000@Atlassian.JIRA>
 <JIRA.12761845.1418673181213@arcas>
Subject: [jira] [Commented] (WW-4433) ConventionUnknownHandler change breaks
 exception handling in interceptors.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/WW-4433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14481854#comment-14481854 ] 

David Williams commented on WW-4433:
------------------------------------

Anybody, is there a projected date for the 2.3.22 release?

> ConventionUnknownHandler change breaks exception handling in interceptors.
> --------------------------------------------------------------------------
>
>                 Key: WW-4433
>                 URL: https://issues.apache.org/jira/browse/WW-4433
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Core Interceptors, Documentation, Plugin - Convention
>    Affects Versions: 2.3.20
>            Reporter: Joseph Wolschon
>            Assignee: Lukasz Lenart
>            Priority: Minor
>             Fix For: 2.3.23
>
>
> Struts 2.3.20 appears to have caused a regression that prevents exceptions thrown from convention-plugin actions from reaching ExceptionMappingInterceptor. This breaks exception handling when using the convention-plugin.
> To Reproduce: 
> * Generate a project struts2-archetype-convention archetype using 2.3.20
> * Throw exception in the action. With 2.3.20, a blank page is shown.
> * Change to 2.3.16.3 and you will get the standard struts2 error page.
> The breaking change appears to have been made in WW-4331. This causes error interceptor code to break (showing a blank page when exceptions are thrown) as DefaultActionInvocation does not catch an exception from the default UnknownHandler implementation execution, which would previously re-throw the original exception back up for the interceptors to catch. 
> Workaround:
> We've created our own UnknownHandler implementation that just throws a new NoSuchMethodException, allowing DefaultActionInvocation to re-throw the original exception so that our error interceptor can again catch it.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)