SAX2: Should SAXException extend IOException?

[David Megginson]

Ray Waldin <rwaldin at pacbell.net> writes:

> from David's SAX2 Exceptions proposal:
> > 5. Have all callbacks that formerly threw SAXException throw
> >    IOException instead.  This should help to avoid a lot of exception
> >    tunneling.
> 
> I don't see the point in a Handler throwing an IOException to a
> Parser in most cases.  That is what this item implies, right?  What
> could a DocumentHandler mean by throwing an IOException during a
> call to startElement?  The I/O has already occurred before the
> handler gets involved.

Well, that's really domain-specific.  It could be that a handler in an
XML I/O library does additional I/O (such as retrieving an external
bitmap) which, from the top-level application's point of view, is
still part of the same I/O process.

In the end, though, this is a relatively minor point.  The important
point, for me, is that SAXException extend IOException -- I think that 
it would be convenient to have the callbacks throw IOException rather
than SAXException (otherwise, other IOExceptions will have to tunnel), 
but it's not a show-stopper if everyone else thinks it's a bad idea.


All the best,


David

-- 
David Megginson                 david at megginson.com
           http://www.megginson.com/

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo at ic.ac.uk the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)