You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by "Dave Brosius (JIRA)" <xe...@xml.apache.org> on 2006/09/10 04:34:22 UTC
[jira] Updated: (XERCESJ-1186) [PATCH] retain exception stack
traces
[ http://issues.apache.org/jira/browse/XERCESJ-1186?page=all ]
Dave Brosius updated XERCESJ-1186:
----------------------------------
Attachment: retain_stack_traces.diff
> [PATCH] retain exception stack traces
> -------------------------------------
>
> Key: XERCESJ-1186
> URL: http://issues.apache.org/jira/browse/XERCESJ-1186
> Project: Xerces2-J
> Issue Type: Improvement
> Affects Versions: 2.8.1
> Reporter: Dave Brosius
> Priority: Minor
> Attachments: retain_stack_traces.diff
>
>
> When a different exception is thrown from a catch block, you lose the original stack trace where the exception occurred, making it more difficult to figure out what went wrong. Add code to initialize the thrown exception's initial cause, so the stack traces are retained.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org