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