Subjects
Home
VOTE Move XML Commons to Xerces
Commented: (XERCESJ 589) Bug with pattern restriction on long strings
: Xerces J 2 8 1 Release on Wednesday, September 13th
: Xerces J 2 9 0 Release on Wednesday, November 22nd
Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
Some consideration about the xerces DOM implementation
Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
retain exception stack traces
Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
Future of NekoHTML
Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
: xml commons external 1 3 04 Release on Wednesday, November 22nd
Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
: xml commons resolver 1 2 Release on Wednesday, November 22nd
Typo in RangeToken java Please check
Validator features
java lang ClassCastException when adopting Node
using the org apache xerces impl xs identity package
Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
Problem with ref attributes and schema validation
Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
Performance problem under load Xerces with Weblogic 9 x
remove ignored memory allocation
Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
Commented: (XERCESJ 977) Null pointer exception during DOM parsing
Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
Commented: (XERCESJ 1201) Initial contribution for StAX Event API
Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
Updated: (XERCESJ 589) Bug with pattern restriction on long strings
StackOverflow
xerces Range unnecessarily not garbage collectable if not detached
Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
Bug in xs:redefine
Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
Google Summer of Code 2007
Xerces J and XInclude relative path issue
Assigned: (XERCESJ 206) Stack overflow when using a schema validation
Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
non overriding equals methoda
Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
Xerces AS3 port
Updated: (XERCESJ 325) Regular Expression; Pattern "| " clause order de
Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
Created: (XERCESJ 1124) Nonspecific schema error message
a bug in xerces
Updated: (XERCESJ 1201) Initial contribution for StAX Event API
Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report
Links
Home
Oracle database error code
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Xerces validation / xsi:schemaLocation problem

Xerces validation / xsi:schemaLocation problem

2003-06-20       - By Webb Roberts
Reply:     1     2     3     4  

I am running up against some strange behavior from Xerces-java 2.4.0.

Basically, I am specifying schema locations with an attribute in the
XML instance, and it is not resolving the locations of the schemas as
I would expect.  I have the following files:

./instance-fails.xml
./instance-validates.xml
./xsd/schema1.xsd
./xsd/schema2.xsd

Schema 1 references schema 2 via an import with no schemaLocation.
The instance that I would expect to validate follows
(instance-fails.xml):

<s1:document
    xmlns:s1='http://something.com/schema1'
    xmlns:s2='http://something.com/schema2'
    xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
    xsi:schemaLocation='http://something.com/schema1 xsd/schema1.xsd
                        http://something.com/schema2 xsd/schema2.xsd'>
  <s2:document/>
</s1:document>

But, that one gives me the error:

WARNING in parsing
  file "file:///..../xsd/schema1.xsd", line 5
  src-import.0: Failed to read imported schema document 'xsd/schema2.xsd'.

However, if the instance is modified as follows
(instance-validates.xml):

<s1:document
    xmlns:s1='http://something.com/schema1'
    xmlns:s2='http://something.com/schema2'
    xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
    xsi:schemaLocation='http://something.com/schema1 xsd/schema1.xsd
                        http://something.com/schema2 schema2.xsd'>
  <s2:document/>
</s1:document>

It validates.  It seems that the filename for schema2 has to be
relative to schema1, instead of relative to the XML instance.  The
only change is the filename for schema2.

Schema 1 is (xsd/schema1.xsd):

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace='http://something.com/schema1'
            xmlns:xsd='http://www.w3.org/2001/XMLSchema'
            xmlns:s2='http://something.com/schema2'>
  <xsd:import namespace='http://something.com/schema2'/>
  <xsd:element name="document">
    <xsd:complexType>
      <xsd:sequence>
        <xsd:element ref='s2:document'/>
      </xsd:sequence>
    </xsd:complexType>
  </xsd:element>
</xsd:schema>

Schema 2 is (xsd/schema2.xsd):

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace='http://something.com/schema2'
            xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
  <xsd:element name="document"/>
</xsd:schema>

The validator I am using is available, as a source and compiled Jar,
from http://justicexml.gtri.gatech.edu/tools/index.html.  It is using
the EntityResolver from org.xml.sax.helpers.DefaultHandler.

Thanks,
Webb

--
Oh, this is the best pizza in a cup ever. This guy is unbelievable. He ran
the old Cup 'o Pizza guy out of business. People come from all over to eat this.


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)