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 "Elliotte Rusty Harold (Jira)" <xe...@xml.apache.org> on 2025/06/27 11:28:00 UTC

[jira] [Closed] (XERCESJ-328) Exception conversion in AbstractSaxParser.java

     [ https://issues.apache.org/jira/browse/XERCESJ-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliotte Rusty Harold closed XERCESJ-328.
-----------------------------------------

> Exception conversion in AbstractSaxParser.java
> ----------------------------------------------
>
>                 Key: XERCESJ-328
>                 URL: https://issues.apache.org/jira/browse/XERCESJ-328
>             Project: Xerces2-J
>          Issue Type: Bug
>          Components: SAX
>    Affects Versions: 2.0.1
>         Environment: Operating System: Other
> Platform: All
>            Reporter: Erwin Achermann
>
> 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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