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

----- Original Message ----- 
From: "Elliotte Rusty Harold" <[email protected]>
To: "Karl Waclawek" <[email protected]>
Cc: <[email protected]>; <[email protected]>
Sent: Friday, February 27, 2004 3:42 PM

> 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.

Yes, I was just thinking out loud.
 
> Even in the indefinite future,. I think the real way to handle this 
> is a stack of nested exceptions thrown by parse().

Would this solve the problem of propagating the error info through
a chain of filters?

Karl



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
List: sax-devel, [email protected]
See:  http://www.saxproject.org/
https://lists.sourceforge.net/lists/listinfo/sax-devel