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 "Michael Glavassevich (JIRA)" <xe...@xml.apache.org> on 2007/08/25 18:31:31 UTC
[jira] Updated: (XERCESJ-1189) Wrap character encoding related
exceptions in the SAXException being reported
[ https://issues.apache.org/jira/browse/XERCESJ-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Glavassevich updated XERCESJ-1189:
------------------------------------------
Fix Version/s: 2.9.1
> 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
> Assignee: Michael Glavassevich
> Priority: Minor
> Fix For: 2.9.1
>
>
> 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: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org