You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2014/06/21 21:40:24 UTC

[jira] [Updated] (TAP5-2133) DefaultRequestExceptionHandler swallows exceptions

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

Jochen Kemnade updated TAP5-2133:
---------------------------------

    Attachment: 0001-TAP5-2133-If-a-new-exception-occurs-during-the-handl.patch

Here comes a patch. I hope you don't mind my meddling with your issue. ;-)

> DefaultRequestExceptionHandler swallows exceptions
> --------------------------------------------------
>
>                 Key: TAP5-2133
>                 URL: https://issues.apache.org/jira/browse/TAP5-2133
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Jochen Kemnade
>            Assignee: Howard M. Lewis Ship
>         Attachments: 0001-TAP5-2133-If-a-new-exception-occurs-during-the-handl.patch
>
>
> If an exception is thrown from the try block in org.apache.tapestry5.internal.services.DefaultRequestExceptionHandler.handleRequestException(Throwable), it is swallowed without any notification. In my case, the problem was a LinkCreationListener's throwing a NPE in a redirected request originating from a previous exception. This was very hard to debug because the NPE didn't show up in any stack trace or log.
> I suggest that either the handler fail completely if the try block throws an exception or at least log it.



--
This message was sent by Atlassian JIRA
(v6.2#6252)