OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] SAX - endDocument() confusion again

[ Lists Home | Date Index | Thread Index ]
  • To: XML Developers List <xml-dev@lists.xml.org>
  • Subject: Re: [xml-dev] SAX - endDocument() confusion again
  • From: David Megginson <dmeggin@attglobal.net>
  • Date: Wed, 03 Mar 2004 09:15:35 -0500
  • In-reply-to: <001101c3fd64$eab0ad30$9e539696@citkwaclaww2k>
  • References: <001101c3fd64$eab0ad30$9e539696@citkwaclaww2k>
  • User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040122 Debian/1.6-1

Karl Waclawek wrote:

> <quote>
> The application must assume that the document is unusable after the parser
> has invoked this method, and should continue (if at all) only for the sake
> of collecting additional error messages: in fact, SAX parsers are free to
> stop reporting any other events once this method has been invoked.
> </quote>
> Since there is no strong and explicit assertion in the SAX docs
> that EndDocument *must* always be called, this would indicate to me
> that in fact there is no such assertion at all, as this looks
> like a proof to the contrary.
> To me this would also mean that any exceptions thrown
> should stop the parser without calling endDocument(), as
> an exception is certainly a stronger error condition than
> a fatalError() call-back that does not throw an exception.
> Any comments? Did I overlook/misunderstand something?

My original intention at the start of SAX development was that endDocument 
would not necessarily be called once the parser was in an error state, but 
the documentation might not have been clear and David Brownell might have 
clarified things the other way after he took over.

All the best,



News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS