|
OpenTop 1.3 | |||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | Cross-Platform C++ | ||||
SUMMARY: CONSTRUCTOR | METHOD | DETAIL: CONSTRUCTOR | METHOD |
#include "ot/sax/ErrorHandler.h"
If a SAX application needs to implement customized error handling, it must implement this interface and then register an instance with the XML reader using the XMLReader::setErrorHandler() method. The parser will then report all errors and warnings through this interface.
WARNING: If an application does not register an ErrorHandler, non-fatal XML parsing errors will go unreported and fatal errors will be cause a SAXParseException to be thrown.
For XML processing errors, a SAX driver will use this interface instead of throwing an exception: it is up to the application to decide whether to throw an exception for different types of errors and warnings. Note, however, that there is no requirement that the parser continue to provide useful information after a call to fatalError().
Method Summary | |
virtual void |
error(const SAXParseException& exception)=0 Receive notification of a recoverable error. |
virtual void |
fatalError(const SAXParseException& exception)=0 Receive notification of a non-recoverable error. |
virtual void |
warning(const SAXParseException& exception)=0 Receive notification of a warning. |
Methods inherited from class ot::ManagedObject |
addRef, getRefCount, onFinalRelease, operator=, release |
Method Detail |
virtual void error(const SAXParseException& exception)=0
This corresponds to the definition of "error" in section 1.2 of the W3C XML 1.0 Recommendation. For example, a validating parser would use this callback to report the violation of a validity constraint. The default behaviour is to take no action.
The SAX parser must continue to provide normal parsing events after invoking this method: it should still be possible for the application to process the document through to the end. If the application cannot do so, then the parser should report a fatal error even if the XML 1.0 recommendation does not require it to do so.
Filters may use this method to report other, non-XML errors as well.
exception
- SAXException
- virtual void fatalError(const SAXParseException& exception)=0
This corresponds to the definition of "fatal error" in section 1.2 of the W3C XML 1.0 Recommendation. For example, a parser would use this callback to report the violation of a well-formedness constraint.
The application must assume that the document is unusable after the parser has invoked this method, and should continue (if at all) only for the sake of collecting additional error messages.
exception
- SAXException
- virtual void warning(const SAXParseException& exception)=0
SAX parsers will use this method to report conditions that are not errors or fatal errors as defined by the XML 1.0 recommendation. The default behaviour is to take no action.
The SAX parser must continue to provide normal parsing events after invoking this method: it should still be possible for the application to process the document through to the end.
Filters may use this method to report other, non-XML warnings as well.
exception
- SAXException
-
|
OpenTop 1.3 | |||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | Cross-Platform C++ | ||||
SUMMARY: CONSTRUCTOR | METHOD | DETAIL: CONSTRUCTOR | METHOD |