[
https://issues.apache.org/jira/browse/TAP5-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129337#comment-13129337
]
Howard M. Lewis Ship commented on TAP5-508:
-------------------------------------------
Tapestry has rules for which exceptions it squashes; in 5.2 and earlier, the
rules are exceptions are squashed if they "add no value".
- An exception whose message is a substring of its containing exception adds no
value
- An exception whose property values are present in the containing exception
adds no value
So you're seeing some of your checked exceptions squashed because the only
difference is the exception class name.
I'm temporarily adding a check: when the exception class name changes, the
frame DOES add value (is not squashed)
> 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
> Assignee: Howard M. Lewis Ship
> Priority: Trivial
> Labels: tapestry5-review-for-closing
> Attachments: TAP509.patch,
> uncheckExceptionSwallowedIfChainingUsed.png,
> uncheckedExceptionTypeNotPrinted.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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
