DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13730>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13730 does not throw an error anymore if schema is unavailable Summary: does not throw an error anymore if schema is unavailable Product: Xerces2-J Version: 2.2.0 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Critical Priority: Other Component: DOM AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] This worked OK until 2.1.0. If the schema is unavailable, the older versions threw an error. 2.2.0 loads the XML without error. Xerces should do schema validation, if one is specified in the XML. And if it is and the schema is not available, then an error should occur. Using these props/features: dbf = DocumentBuilderFactory.newInstance(); dbf.setNamespaceAware(true); dbf.setValidating(true); dbf.setAttribute("http://apache.org/xml/features/validation/dynamic";, new Boolean(true)); dbf.setAttribute("http://apache.org/xml/features/validation/schema";, new Boolean(true)); dbf.setAttribute("http://xml.org/sax/features/validation";, new Boolean(true)); --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
