[
https://issues.apache.org/jira/browse/TAP5-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040956#comment-14040956
]
Hudson commented on TAP5-2133:
------------------------------
FAILURE: Integrated in tapestry-trunk-freestyle #1251 (See
[https://builds.apache.org/job/tapestry-trunk-freestyle/1251/])
TAP5-2133: DefaultRequestExceptionHandler swallows exceptions (hlship: rev
24344bed915715a5c2424edfeab9bbb5f12f7089)
*
tapestry-core/src/main/java/org/apache/tapestry5/internal/services/DefaultRequestExceptionHandler.java
> 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
> Fix For: 5.4
>
> 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)
