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 bu...@apache.org on 2003/04/08 20:17:56 UTC
DO NOT REPLY [Bug 18828] -
setEntityResolver(null) throws NulPointerException
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=18828>.
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=18828
setEntityResolver(null) throws NulPointerException
neilg@ca.ibm.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |LATER
------- Additional Comments From neilg@ca.ibm.com 2003-04-08 18:17 -------
Hi Elliotte. Some time between SAX 2.0 and 2.0.1, the behaviour of XMLReaders
when setEntityResolver is passed with a null parameter was changed: in 2.0, an
NPE was supposed to be thrown; in 2.0.1, the parser was supposed to return to
its default behaviour. As has been noted before on the SAX development list,
JAXP 1.2 requires parsers to conform strictly to SAX 2.0; among many other
things, its TCK tests for this behaviour. So, until JAXP is updated to
reference SAX 2.0.1, there's nothing we can do about this bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org