Cart
[Home] [By Thread] [By Date] [Recent Entries]
Rajiv Mordani writes:
> I am not sure what the intent is of having IOException. I think
> SAXException seems appropriate to me..
I'd like to hear as many opinions on this point as possible. What is
the rationale for *not* deriving SAXException from IOException when
(for example) java.net.MalformedURLException and
java.util.zip.ZipException are derived from IOException?
I especially like the idea that higher-level libraries could have
void importXML (String uri) throws IOException;
without the application's having any direct dependency on SAX
interfaces. It could accomplish the same thing by having a
SAXExceptionAdapter that embeds the SAXException and extends
IOException, but that seems like a lot of unnecessary fuss for a very
common case.
Opinions?
All the best,
David
--
David Megginson david@m...
http://www.megginson.com/
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo@i... the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
