• To: Jochen Wiedmann <joe@i...>
• Subject: Re: SAX/Java Proposed Changes
• From: Elliotte Rusty Harold <elharo@m...>
• Date: Mon, 8 Mar 2004 16:12:17 -0500
• Cc: xml-dev@l..., sax-devel@l...
• In-reply-to: <404CD7D4.90106@i...>
• References: <1078627030.23151.ezmlm@l...><404B5CA1.7070000@i...> <p06010203bc71316af8e7@[192.168.254.4]><404CD7D4.90106@i...>

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.  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. The client can't 
do that so easily when the parser is choosing to end parsing. But 
maybe you were trying to say something else and I'm jusat not seeing 
it?
-- 

   Elliotte Rusty Harold
   elharo@m...
   Effective XML (Addison-Wesley, 2003)
   http://www.cafeconleche.org/books/effectivexml
   http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA

• Follow-Ups:
  • Re: SAX/Java Proposed Changes
    • From: "Karl Waclawek" <karl@w...>

• References:
  • Re: SAX/Java Proposed Changes
    • From: Jochen Wiedmann <joe@i...>
  • Re: SAX/Java Proposed Changes
    • From: Elliotte Rusty Harold <elharo@m...>
  • Re: SAX/Java Proposed Changes
    • From: Jochen Wiedmann <joe@i...>

• Prev by Date: Re: SAX/Java Proposed Changes
• Next by Date: Re: SAX/Java Proposed Changes
• Previous by thread: Re: SAX/Java Proposed Changes
• Next by thread: Re: SAX/Java Proposed Changes
• Index(es):
  • Date
  • Thread