[Home] [By Thread] [By Date] [Recent Entries]
David Megginson wrote: > > Following up on a long-ago suggestion from (I think) David Brownell, [ not that I recall, FWIW ] > I'm consider adding an extra method, validationError(), to the SAX2 > ErrorHandler. That way, we'd have the following methods: > > warning - any kind of non-fatal warning > error - an optionally-reportable error of some kind, or an error > from outside the XML 1.0 domain (such as a Namespace error > that doesn't affect well-formedness) > validationError - an error in schema validation > fatalError - a well-formedness error > > Does this work? Hmm, if it's schema-specific, then shouldn't it be "schemaError" ? Were I to ask for more specific indications of DTD (or schema) related errors, I'd use subclasses of SAXParseException, passed to error(). Note that this addresses the same issue that the integer code in exceptions addresses, but it does it in a different way. I'd really go for only one solution to such problems. - Dave 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/ and on CD-ROM/ISBN 981-02-3594-1 To unsubscribe, mailto:majordomo@i... the following message; unsubscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|

Cart



