[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: SAX: Error Reporting (question 4 of 10)
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 more errors. Paul Prescod -- http://itrc.uwaterloo.ca/~papresco 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@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|