[jira] Commented: (TAP5-508) Same reporting behaviour between unchecked and checked Exceptions

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAP5-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678911#action_12678911 ] 

Howard M. Lewis Ship commented on TAP5-508:
-------------------------------------------

Perhaps I could change presentation of "duplicate" exceptions to work like the new approach to stack frames: initially hidden (but still present), revealed via a checkbox.

> 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
>
>         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.