[saxdotnet-devel] ErrorHandler arguments
Brought to you by:
jeffrafter,
kwaclaw
From: Karl W. <ka...@wa...> - 2005-01-03 18:35:01
|
On xml-dev there is a thread called "[xml-dev] SAXException, checked, buy why?". The problem that came up is what to do when trying to pass recoverable errors to the application? Alan Gutierrez thinks one is not allowed to use error handler call-backs, but I think that maybe this is just a result of underspecification. In any case, the objects passed to the error call-backs are SAXParseException objects in Java, and ParseError objects in SAX for .NET. I am thinking we should rename the class from ParseError to SAXError, as errors from application code (as you might have in your content handlers) are not really parse errors, and you should still be allowed to pass them to the error handlers, to avoid throwing an exception. However, all members of ParseError (or SAXParseException ) are geared towards errors that can occur when parsing an XML document (publicId, SystemId, Line/ColumnNumber, etc.). So, what to do? Should we stick with the limitation that only parse errors can be reported to the error handlers? Is that not rather limiting? Karl |