Kbase 37562: What XML/SAX callback error procedures are invoked by the parser?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/2/2001 |
|
Solution ID: P7562
GOAL:
What XML/SAX callback error procedures are invoked by the parser?
FIX:
XML/SAX has error procedures, called "callbacks" that are invoked by the parser. The names of the error procedures -- Warning, Error, FatalError -- do not
intuitively describe when they are invoked. This can cause confusion in
interpreting the message and its impact.
For example, an XML/SAX error might be generated in which the XML does not match the structure declared in your DTD. This result is somewhat misleading since
it can seem to imply a FatalError Callback or a Progress bug when in fact it does not. This is not a bug because in the XML/SAX world, XML not matching a
DTD is considered an Error rather than a FatalError.
The list of errors below identifies which types of errors cause which types
of error callbacks.
XML/SAX Error Callbacks
The following are examples of the types of "Errors" reported by
each of the ErrorHandler Callbacks according to the XML/SAX
specification and parser.
-- Warning Callback
Duplicate Attribute List declaration in DTD
Duplicate Notation declaration in DTD
Contradictory Encoding
DTD contains an element whose element type is not defined
DTD contains an attribute whose element type is not defined
-- Error Callback
Validation errors, the XML does not match the structure declared in
the associated DTD.
XML version mismatches
-- FatalError Callback
Violations of XML's well-formed rules, that is, not having
matching begin and end tags.
Unrecognized character encoding
Illegal use of entity or character references