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 7:33 PM


> At 6:43 PM -0500 2/27/04, Karl Waclawek wrote:
> 
> >>  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?
> 
> I think it could. Each layer just catches the exception thrown by the 
> underlying layer, wraps it in a new exception, and tosses it to the 
> layer above it (unless it wants to fix the problem somehow. Right now 
> I'm toying with the idea of an XMLFilter that fixes all the bugs I've 
> uncovered in Xerces, including incorrect exception handling.)

I thought of the reverse direction.
How would a filter *down* the chain deal with an "end of parsing"
if it doesn't know why parsing stopped. Was it the end of the document?
Was there an exception? I think someone else pointed that out already,
but I missed the name.

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