Consider a document such as the following:
<root> <child1/> <child2> </root>
Following up on this, I withdraw my original report that Xerces was not reporting all the content before the first well-formedness error. It was, but the unusual nature of the code caused me to misattribute to Xerces a different bug. My apologies.
However, I do think the SAX ContentHandler documentation still needs to be clearer, that well-formedness errors should not be reported until after all preceding content has been reported through the usual mechanism. This strikes me as especially important for filters that sit on top of other API such as StAX or XNI where it might be possible for a well-formedness error to be detected in one thread before the queue of SAX events has been emptied in another thread.
The current documentation says that the order of the events in the ContentHandler interface is important, but it doesn't say that for events in the ErrorHandler interface. There are other ordering issues left unsaid as well. For instance, I can't find any rule that comments reported by the LexicalHandler need to be reported at their appropriate position.
I think some general language is needed such as:
The order of events in the ConetentHandler, ErrorHandler, and LexicalHandler interfaces is very important, and mirrors the order of information in the document itself. For example, all of an element's content (character data, comments, processing instructions, and/or subelements) will appear, in order, between the startElement event and the corresponding endElement event.
--
Elliotte Rusty Harold [EMAIL PROTECTED] Processing XML with Java (Addison-Wesley, 2002) http://www.cafeconleche.org/books/xmljava http://www.amazon.com/exec/obidos/ISBN%3D0201771861/cafeaulaitA
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
