Incorrect JavaDoc for ContentHandler.startDocument

Elliotte Rusty Harold <[email protected]>
Newsgroups gmane.text.xml.sax.devel
Message-ID <p04330102b9ddb2e7a0f2@[192.168.254.4]>
The JavaDoc for the startElement() method in Contenthandler states:


The SAX parser will invoke this method only once, before any other 
methods in this interface or in DTDHandler (except for 
setDocumentLocator).

I believe it should instead state:

The SAX parser will invoke this method only once per document, before 
any other methods in this interface or in DTDHandler (except for 
setDocumentLocator).

Reasoning: If an XMLReader parses multiple documents in series, then 
it will quite naturally invoke startDocument() multiple times.

The endDocument() method has the same problem.
-- 

+-----------------------+------------------------+-------------------+
| Elliotte Rusty Harold | [email protected] | Writer/Programmer |
+-----------------------+------------------------+-------------------+
|          XML in a  Nutshell, 2nd Edition (O'Reilly, 2002)          |
|              http://www.cafeconleche.org/books/xian2/              |
|  http://www.amazon.com/exec/obidos/ISBN%3D0596002920/cafeaulaitA/  |
+----------------------------------+---------------------------------+
|  Read Cafe au Lait for Java News:  http://www.cafeaulait.org/      |
|  Read Cafe con Leche for XML News: http://www.cafeconleche.org/    |
+----------------------------------+---------------------------------+


-------------------------------------------------------
This sf.net email is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ad.doubleclick.net/clk;4729346;7592162;s?http://www.sun.com/javavote
_______________________________________________
List: sax-devel, [email protected]
See:  http://www.saxproject.org/
https://lists.sourceforge.net/lists/listinfo/sax-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.