|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: SAX - endDocument() confusion again
----- Original Message ----- From: "Elliotte Rusty Harold" <elharo@m...> To: "Karl Waclawek" <karl@w...> Cc: <xml-dev@l...>; <sax-devel@l...> 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
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
|||||||||

Cart








