tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TAP5-508) Same reporting behaviour between unchecked and checked Exceptions
Date Wed, 04 Mar 2009 20:39:56 GMT

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

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

Filtering out the duplicate exceptions is intentional, otherwise the exception report page
gets overwhelmingly cluttered with redundant data.

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


Mime
View raw message