You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "manuel aldana (JIRA)" <ji...@apache.org> on 2009/02/10 01:07:59 UTC
[jira] Created: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
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
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.
[jira] Updated: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "manuel aldana (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "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.
[jira] Resolved: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "manuel aldana (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
manuel aldana resolved TAP5-508.
--------------------------------
Resolution: Fixed
Fix Version/s: 5.1.0.0
see patch attachement comment
> 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.
[jira] Updated: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-508:
--------------------------------------
Fix Version/s: (was: 5.1.0.0)
5.1
> 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.
[jira] Updated: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "manuel aldana (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
manuel aldana updated TAP5-508:
-------------------------------
Attachment: uncheckExceptionSwallowedIfChainingUsed.png
Yes, I still think it is inconsistent behaviour (error page should be transparent, whether user threw a checked or an unchecked exception himself).
Even worse, when using exception-chaining it happens that unchecked application exception is not shown at all and is being swallowed (see screenshot uncheckExceptionSwallowedIfChainingUsed.png).
I tend to use unchecked exception in my application and use exception chaining a lot. I remember that I was quite confused that my application exception did not show up on the error page.
Reason seems to be that first top-level exception is filtered in error page. The easiest fix was to use this last RuntimeException wrap.
Is this fix really an issue? What speaks against 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, 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.
[jira] Commented: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "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=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.
[jira] Commented: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "Filip S. Adamsen (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "manuel aldana (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "manuel aldana (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
manuel aldana updated TAP5-508:
-------------------------------
Attachment: TAP509.patch
patch, resolution: wrapping unchecked RuntimeException to another RuntimeException. This way the reporting is consistent between checked and unchecked.
> 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.
[jira] Updated: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "Robert Zeigler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Zeigler updated TAP5-508:
--------------------------------
Fix Version/s: (was: 5.1)
> 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: 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.
[jira] Updated: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "manuel aldana (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
manuel aldana updated TAP5-508:
-------------------------------
Attachment: TAP509.patch
patch, resolution: wrapping unchecked RuntimeException to another RuntimeException. This way the reporting is consistent between checked and unchecked.
> 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.
[jira] Commented: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "Filip S. Adamsen (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "manuel aldana (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
manuel aldana updated TAP5-508:
-------------------------------
Attachment: uncheckExceptionSwallowedIfChainingUsed.png
Yes, I still think it is inconsistent behaviour (error page should be transparent, whether user threw a checked or an unchecked exception himself).
Even worse, when using exception-chaining it happens that unchecked application exception is not shown at all and is being swallowed (see screenshot uncheckExceptionSwallowedIfChainingUsed.png).
I tend to use unchecked exception in my application and use exception chaining a lot. I remember that I was quite confused that my application exception did not show up on the error page.
Reason seems to be that first top-level exception is filtered in error page. The easiest fix was to use this last RuntimeException wrap.
Is this fix really an issue? What speaks against 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, 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.
[jira] Updated: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "Robert Zeigler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Zeigler updated TAP5-508:
--------------------------------
Fix Version/s: (was: 5.1)
> 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: 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.
[jira] Reopened: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "manuel aldana (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
manuel aldana reopened TAP5-508:
--------------------------------
> 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.
[jira] Commented: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "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.
[jira] Commented: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "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=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.
[jira] Updated: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-508:
--------------------------------------
Fix Version/s: (was: 5.1.0.0)
5.1
> 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.
[jira] Commented: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "Filip S. Adamsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672394#action_12672394 ]
Filip S. Adamsen commented on TAP5-508:
---------------------------------------
Okay, I see now. I just tried chaining 3 runtime exception and as you said, only the innermost one was shown. That's odd, and certainly not what I would expect.
I still don't like wrapping the whole thing in another exception, though. I believe fixing the root cause (no pun intended) is the way to go instead.
> 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, 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.
[jira] Commented: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "Filip S. Adamsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672394#action_12672394 ]
Filip S. Adamsen commented on TAP5-508:
---------------------------------------
Okay, I see now. I just tried chaining 3 runtime exception and as you said, only the innermost one was shown. That's odd, and certainly not what I would expect.
I still don't like wrapping the whole thing in another exception, though. I believe fixing the root cause (no pun intended) is the way to go instead.
> 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, 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.
[jira] Resolved: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "manuel aldana (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
manuel aldana resolved TAP5-508.
--------------------------------
Resolution: Fixed
Fix Version/s: 5.1.0.0
see patch attachement comment
> 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.
[jira] Reopened: (TAP5-508) Same reporting behaviour between
unchecked and checked Exceptions
Posted by "manuel aldana (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
manuel aldana reopened TAP5-508:
--------------------------------
> 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.