[
https://issues.apache.org/jira/browse/TAP5-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
manuel aldana updated TAP5-508:
-------------------------------
Attachment: uncheckExceptionSwallowedIfChainingUsed.png
Yes, I still think it is inconsistent behaviour (error page should be
transparent, whether user threw a checked or an unchecked exception himself).
Even worse, when using exception-chaining it happens that unchecked application
exception is not shown at all and is being swallowed (see screenshot
uncheckExceptionSwallowedIfChainingUsed.png).
I tend to use unchecked exception in my application and use exception chaining
a lot. I remember that I was quite confused that my application exception did
not show up on the error page.
Reason seems to be that first top-level exception is filtered in error page.
The easiest fix was to use this last RuntimeException wrap.
Is this fix really an issue? What speaks against it?
> 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.
