[
Lists Home |
Date Index |
Thread Index
]
----- Original Message -----
From: "Elliotte Rusty Harold" <elharo@metalab.unc.edu>
To: "Karl Waclawek" <karl@waclawek.net>
Cc: <xml-dev@lists.xml.org>; <sax-devel@lists.sourceforge.net>
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
|
