You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "manuel aldana (JIRA)" <ji...@apache.org> on 2009/02/10 01:09:59 UTC

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

     [ https://issues.apache.org/jira/browse/TAP5-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

manuel aldana updated TAP5-508:
-------------------------------

    Attachment: uncheckedExceptionTypeNotPrinted.png

example for inconsistent reporting between checked and unchecked (type is not printend).

> 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
>         Attachments: 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.
-
You can reply to this email to add a comment to the issue online.