You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by bu...@apache.org on 2002/10/17 14:37:35 UTC
DO NOT REPLY [Bug 13730] New: -
does not throw an error anymore if schema is unavailable
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: xerces-j-dev@xml.apache.org
ReportedBy: thomas@boerkel.de
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: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org