[
https://issues.apache.org/jira/browse/XERCESJ-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Glavassevich resolved XERCESJ-1189.
-------------------------------------------
Resolution: Fixed
I just implemented this in SVN. The CharConversionException is now available
from SAXException.getException().
> Wrap character encoding related exceptions in the SAXException being reported
> -----------------------------------------------------------------------------
>
> Key: XERCESJ-1189
> URL: https://issues.apache.org/jira/browse/XERCESJ-1189
> Project: Xerces2-J
> Issue Type: New Feature
> Components: SAX
> Affects Versions: 2.8.1
> Reporter: Stanimir Stamenkov
> Assigned To: Michael Glavassevich
> Priority: Minor
>
> During parsing (XMLReader.parse()), when a character encoding problem happens
> on the input (e.g. a java.io.CharConversionException is thrown) it is
> reported as SAXException but any trace from the original exception is lost
> (except the exception message) thus making it harder to recognize the initial
> problem. Making the original exception accessible through
> SAXException.getException() (and/or Exception.getCause()) will help in
> recognizing character encoding problems easier.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
