[
Lists Home |
Date Index |
Thread Index
]
- From: David Megginson <david@megginson.com>
- To: XMLDev list <xml-dev@ic.ac.uk>
- Date: Tue, 21 Dec 1999 09:21:58 -0500 (EST)
Now that the Namespace-support discussion is pretty-much wrapped up
(aside from some aesthetic questions), I'd like to move on to the
question of exceptions, which I hope will be considerably less
controversial.
For SAX2, I'm proposing the following major changes in exceptions:
1. SAXException extends IOException.
2. Add SAXNotRecognizedException, for a feature or property name
that's not recognized. Extends SAXException.
3. Add SAXNotSupportedException, for a request that the parser doesn't
support. Extends SAXException.
4. Modify SAXParseException so that it also has an integer value
containing the error number. If there ever is a standard catalog
of XML (and related) errors, we can use this to hold the number.
5. Have all callbacks that formerly threw SAXException throw
IOException instead. This should help to avoid a lot of exception
tunneling.
Any issues? I know that a few people suggested extending
IOException back in the SAX 1.0 design a year and a half ago, and
after doing a lot of implementation on top of SAX, I now agree with
them.
All the best,
David
--
David Megginson david@megginson.com
http://www.megginson.com/
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@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@ic.ac.uk the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)
|