SAX: Error Reporting (question 4 of 10)
papresco at technologist.com
Sun Jan 4 15:00:46 GMT 1998
James Clark wrote:
> I feel pretty strongly that the right way to handle fatal XML errors in
> Java in a production-oriented interface is with an exception and that
> SAX needs to define an exception to cover fatal XML errors. The
> exception should extend IOException so that it works with the
> java.net.ContentHandler stuff.
It seems very easy to map from a notWellFormed event to a notWellFormed
exception and essentially impossible to map from the exception back into
an event (with context etc.). I would thus prefer to leave it up to the
application programmer whether to throw an exception or try and gather
Art is always at peril in universities, where there are so many people,
young and old, who love art less than argument, and dote upon a text
that provides the nutritious pemmican on which scholars love to chew.
-- Robertson Davies in "The Cunning Man"
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/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
More information about the Xml-dev