[
https://issues.apache.org/jira/browse/TAP5-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672394#action_12672394
]
Filip S. Adamsen commented on TAP5-508:
---------------------------------------
Okay, I see now. I just tried chaining 3 runtime exception and as you said,
only the innermost one was shown. That's odd, and certainly not what I would
expect.
I still don't like wrapping the whole thing in another exception, though. I
believe fixing the root cause (no pun intended) is the way to go instead.
> Same reporting behaviour between unchecked and checked Exceptions
> -----------------------------------------------------------------
>
> Key: TAP5-508
> URL: https://issues.apache.org/jira/browse/TAP5-508
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.18
> Reporter: manuel aldana
> Priority: Trivial
> Fix For: 5.1.0.0
>
> Attachments: TAP509.patch, uncheckedExceptionTypeNotPrinted.png,
> uncheckExceptionSwallowedIfChainingUsed.png
>
>
> Unchecked exceptions are reported differently on Exception reporting page.
> This should be changed, because many applications have convention to use an
> unchecked exception hierachy.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
