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=13614>. 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=13614 Setting the external-schemaLocation property does not seem to work Summary: Setting the external-schemaLocation property does not seem to work Product: Xerces2-J Version: 2.2.0 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: XML Schema Structures AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Setting the external-schemaLocation property for Xerces 2.2 does not resolve schema locations. Xerces will resolve a schema location if a reference to it exists in the instance document that it is validating (via the xsi:schemaLocation attribute). This was observed using both the JAXP and native (DOMParser, SAXParser) interfaces. This was not observed under Xerces 2.1 or Xerces 1.4.4 -- under both libraries, setting the schemaLocation property via code worked to resolve locations. Under all libraries, however, the JAXP interface for isValidating() only seems to turn on validation through a DTD grammar, regardless of whether the schemaLocation property is set (via code OR via xsi:schemaLocation in the instance). Is this a bug in the JAXP interface implementations, or is this functionality expected? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
