logo       
Google Custom Search

Related Msgs: audio.musicbrai...    enbd.general/20...    ietf.idr/2002-0...    java.ant-contri...    gnu.make.genera...    qplus.devel/200...    video.freevo.cv...    os.netbsd.ports...    yellowdog.gener...    xfree86.cvs/200...    search.nutch.us...    freedesktop.xse...    programming.swi...    capabilities.ge...    telephony.pbx.a...    mail.sylpheed.c...    db.firebase.por...    boot-loaders.u-...    recreation.radi...    netbsd.bugs/200...    web.zope.plone....    user-groups.lin...   

[jira] Resolved: (XERCESJ-1189) Wrap character encoding related exceptions : msg#00011

Subject: [jira] Resolved: (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 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.



Try Searching:
servers, voip, java, networking, microsoft ...
<Prev in Thread] Current Thread [Next in Thread>