when using latest xerces2 (CVS) I get two error handler calls for a single failed constraint. Can someone please explain if this was indended? I don't see a good reason for that.
org.xml.sax.SAXParseException: cvc-minInclusive-valid: Value '2' is not facet-valid with respect to minInclusive '50'. org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:232) org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:173) org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:362) ... and org.xml.sax.SAXParseException: cvc-type.3.1.3: The value '2' of element 'number' is not valid. org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:232) org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:173) org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:362) ... An I am also wondering if it is already possible to get some more information from the SAXException. a) the full path to the node that cause the error b) not just a text message but an object (some kind of constraint or facet object) that makes machine based processing based on the validation result possible. AFAICS the current information is only useful if you want to pass it directly to a user. I'd need to parse it to get the desired information. (but that would ugly as hell...) Or is there already a way to get the information: minInclusive value-is: 2 value-is-supposed-to-be: 50 out of the above exception? Thanks -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
