DO NOT REPLY [Bug 9337] New: - Exception conversion in AbstractSaxParser.java

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9337>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9337

Exception conversion in AbstractSaxParser.java

           Summary: Exception conversion in AbstractSaxParser.java
           Product: Xerces2-J
           Version: 2.0.1
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: SAX
        AssignedTo: xerces-j-dev@xml.apache.org
        ReportedBy: erwin.achermann@switzerland.org


Hi, i was implementing my own Handler, which generated an (errrr) 
NullPointerExcpetion in StartDocument() callback. This was my bug, BUT 
AbstracSaxParser.parse() chatches my Exception and rethrows it. This makes it 
look like line 'throw new SAXException(ex);' had a NullPointerException. MayBe 
there is a good reason to catch any Exception here, but i don't understand it. 
I would expect a 'exception tunneling', i.e. exceptions in the users callback 
should be recognizable as such. Thanks for your time.

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org