Re: Passing null to setFooHandler
Michael Glavassevich <[email protected]> Sun, 25 Apr 2004 15:05:34 -0400
| Newsgroups | gmane.text.xml.sax.devel |
|---|---|
| Message-ID | <OF47348B94.9D36B6CD-ON85256E81.006881AC-85256E81.0068E094@ca.ibm.com> |
[email protected] wrote on 04/25/2004 02:21:11 PM: > > > > I suggest we add verbiage like the following to each of the setter > > methods in XMLReader: > > > > An application may pass null to this method to remove the currently > > registered ContentHandler. In this case, the parser must stop using the > > old handler immediately. A NullPointerException is not thrown. > > Make sense to. Is that really not documented? The javadoc for the setFooHandler methods currently says: "Applications may register a new or different handler in the middle of a parse and the SAX parser must begin using the new handler immediately." Does more really need to be said here? The NullPointerException condition was removed in SAX 2.0.1. > Karl > > > ------------------------------------------------------- > This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek > For a limited time only, get FREE Ground shipping on all orders of $35 > or more. Hurry up and shop folks, this offer expires April 30th! > http://www.thinkgeek.com/freeshipping/?cpg=12297 > _______________________________________________ > List: sax-devel, [email protected] > See: http://www.saxproject.org/ > https://lists.sourceforge.net/lists/listinfo/sax-devel Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [email protected] E-mail: [email protected]