You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (Assigned) (JIRA)" <ji...@apache.org> on 2011/10/18 01:31:11 UTC
[jira] [Assigned] (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 ]
Howard M. Lewis Ship reassigned TAP5-508:
-----------------------------------------
Assignee: Howard M. Lewis Ship
> 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