[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3797) ConversationInterceptor.aroundInvoke broken stacktrace
Francisco Jose Peredo Noguez (JIRA)
jira-events at lists.jboss.org
Fri Jan 9 12:51:04 EST 2009
[ https://jira.jboss.org/jira/browse/JBSEAM-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12447034#action_12447034 ]
Francisco Jose Peredo Noguez commented on JBSEAM-3797:
------------------------------------------------------
Mmmm, I don't see any value in breaking the stacktrace... ;-)
I don't really want to "wrap the exception ", what I want is to preserve the full stacktrace so that I can trace the real root cause of the problem by reading the stacktrace (instead of having to start a step by step debugger).
Do you know of another way of preserving the stacktrace?
> ConversationInterceptor.aroundInvoke broken stacktrace
> ------------------------------------------------------
>
> Key: JBSEAM-3797
> URL: https://jira.jboss.org/jira/browse/JBSEAM-3797
> Project: Seam
> Issue Type: Bug
> Reporter: Francisco Jose Peredo Noguez
> Assignee: Norman Richards
> Fix For: 2.1.2.CR1
>
> Attachments: patch.txt
>
>
> catch (Exception e)
> {
> if ( isEndConversationRequired(e) )
> {
> endConversation(false, false);
> }
> throw e; //<---HERE!
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list