You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Simone Tripodi (JIRA)" <ji...@apache.org> on 2011/06/27 12:00:47 UTC
[jira] [Commented] (DIGESTER-85) [digester] Include filename or uri
if Digester.parse(File file or String uri throws a SAXException
[ https://issues.apache.org/jira/browse/DIGESTER-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055441#comment-13055441 ]
Simone Tripodi commented on DIGESTER-85:
----------------------------------------
Fixed on Digester3 /trunk, see [r1140083|http://svn.apache.org/viewvc?view=revision&revision=1140083].
There's no need to decorate the thrown exception, filename or uri have been logged at error level: since the request is focused on monitoring errors from 3rd-parties Digester use, logging which resource caused the error is more than enough.
> [digester] Include filename or uri if Digester.parse(File file or String uri throws a SAXException
> --------------------------------------------------------------------------------------------------
>
> Key: DIGESTER-85
> URL: https://issues.apache.org/jira/browse/DIGESTER-85
> Project: Commons Digester
> Issue Type: Improvement
> Environment: Operating System: All
> Platform: All
> Reporter: Erik Meade
> Priority: Minor
>
> Would make debugging easier.
> A try catch SAXException block around the getXMLReader().parse(input); statements in the parse
> File and parse(String would allow the SAX Exception to be caught, taken apart, an error statement
> with file or uri added, and thrown.
> But how to capture the first stack trace? Use NestedExceptions from jakarta-commons-lang? Use
> org.apache.commons.lang.exception.ExceptionUtils.getStackTrace and and cram the first stack
> trace in the with new SAXExceptions? Or avoid the new dependecy on lang and do something
> else?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira