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/Java Proposed Changes

[ Lists Home | Date Index | Thread Index ]

----- Original Message ----- 
From: "Elliotte Rusty Harold" <elharo@metalab.unc.edu>
To: "Jochen Wiedmann" <joe@ispsoft.de>
Cc: <xml-dev@lists.xml.org>; <sax-devel@lists.sourceforge.net>
Sent: Monday, March 08, 2004 4:12 PM

> At 9:30 PM +0100 3/8/04, Jochen Wiedmann wrote:
> >Elliotte Rusty Harold wrote:
> >
> >>  Then your code will break when used with some of today's parsers 
> >>which do call endDocument() after a fatal error.. :-(
> >
> I'm not sure what this program is supposed to demonstrate. One of the 
> conclusions I think we're reaching is that if a client supplied 
> method such as startDocument() throws an exception, then endDocument 
> (and fatalError()) are not called. 

In that case, endDocument() should also not be called in the
case of a parser generated exception. I don't see why one should
treat a client generated exception differently, it would just
make client code more complicated.

> endDocument() and fatalError() 
> are for the use of the parser only. If the client chooses to 
> prematurely abort processing by tossing an exception, then the client 
> has the responsibility to clean up before doing so. 

I think cleanup responsibility is determined by what you
"own", not by where the exception originates.



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

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