• To: "Karl Waclawek" <karl@w...>
• Subject: Re: SAX - endDocument() confusion again
• From: Elliotte Rusty Harold <elharo@m...>
• Date: Fri, 27 Feb 2004 15:42:05 -0500
• Cc: <xml-dev@l...>, <sax-devel@l...>
• In-reply-to: <00a901c3fd70$16ff7230$9e539696@citkwaclaww2k>
• References: <001101c3fd64$eab0ad30$9e539696@citkwaclaww2k><016501c3fd6b$893dc2c0$6403a8c0@ARIMATHEA><00a901c3fd70$16ff7230$9e539696@citkwaclaww2k>

At 3:27 PM -0500 2/27/04, Karl Waclawek wrote:


>What about this then:
>
>- Add an error argument to endDocument, like in
>
>   public void endDocument(SAXParseException exception)
>                 throws SAXException
>
>   which can be null.

This would be backwards incompatible. Maybe if at some point in the 
future it's decided we need a backwards incompatible version of SAX, 
but not feasible for the immediate future in the Java 1.5 time frame.

Even in the indefinite future,. I think the real way to handle this 
is a stack of nested exceptions thrown by parse().

-- 

   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 - endDocument() confusion again
    • From: "Karl Waclawek" <karl@w...>

• References:
  • SAX - endDocument() confusion again
    • From: "Karl Waclawek" <karl@w...>
  • Re: SAX - endDocument() confusion again
    • From: "Jeff Rafter" <lists@j...>
  • Re: SAX - endDocument() confusion again
    • From: "Karl Waclawek" <karl@w...>

• Prev by Date: Re: [Sax-devel] SAX - endDocument() confusion again
• Next by Date: Re: [Sax-devel] SAX - endDocument() confusion again
• Previous by thread: Re: SAX - endDocument() confusion again
• Next by thread: Re: SAX - endDocument() confusion again
• Index(es):
  • Date
  • Thread