[ http://issues.apache.org/jira/browse/XERCESJ-1186?page=comments#action_12433731 ] Michael Glavassevich commented on XERCESJ-1186: -----------------------------------------------
Right. This is approximately what was being considered for SAXException. David Megginson wanted some feedback [1] from the community before making the change but very few people responded. It was hoped that this could be included in JAXP 1.4 (Java SE 6) but it's probably too late for that now. [1] http://www.megginson.com/blogs/quoderat/archives/2006/03/12/rfc-java-sax-exceptions-and-new-minor-sax-version/ > [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.0 > 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
