[
https://issues.apache.org/jira/browse/TAP5-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672118#action_12672118
]
Filip S. Adamsen commented on TAP5-508:
---------------------------------------
The class name (or exception type, if you will) is part of the message created
when you chain exceptions - it's not something Tapestry does, just regular Java.
I don't see what the problem is, anyway - the type of the exception is
displayed right below the line you included in your screenshot - and I
certainly don't want Tapestry to wrap all RuntimeExceptions in yet another
RuntimeException because of it.
> 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.0.0
>
> Attachments: TAP509.patch, 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.
