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.
Keyrefs and mixed content

Keyrefs and mixed content

2003-08-05       - By Laura Smith
Reply:     1     2     3  

Yes, that is the error I got.

Thanks for the help!
Laura

-----Original Message-----
From: Sandy Gao [mailto:sandygao@(protected)]
Sent: Tuesday, August 05, 2003 4:55 PM
To: xerces-j-user@(protected)
Subject: Re: Keyrefs and mixed content


Is the following the error message you got?

[Error] ...:8:43: cvc-id.3: A field of identity constraint 'ZoneToZoneName'
matched element 'Zone', but this element does not have a simple type.

It's required that all elements that match the "field"s of a "key/keyref"
to have a simple type. In your example, the element <Zone>Unite
States</Zone> matches a field in the keyref, but it has a complex type.

This seems to be a bug fixed after 2.0.1.

HTH,
Sandy Gao
Software Developer, IBM Canada
(1-905) 413-3255
sandygao@(protected)




                     "Laura Smith"
                     <Laura.Smith@(protected)        To:       <xerces-j-user@(protected)
.apache.org>
                     com>                     cc:
                                              Subject:  Keyrefs and mixed
content
                     08/01/2003 11:55
                     AM
                     Please respond to
                     xerces-j-user





The following schema and instance validated properly with the following:


Name: org/apache/xerces
Specification-Title: Java API for XML Processing
Specification-Vendor: Sun Microsystems Inc.
Implementation-Vendor: Apache Software Foundation
Implementation-URL: http://xml.apache.org/xerces2-j
Specification-Version: 1.2
Implementation-Version: Xerces-J_2_0_1_01
Implementation-Title: org.apache.xerces
Comment: Xerces parser implementing JAXP


Why won't it validate properly with this version?


Name: org/apache/xerces/impl/Version
Comment: @(protected)@ for http://xml.apache.org/xerces2-j
Implementation-Title: org.apache.xerces.impl.Version
Implementation-Version: 2.5.0
Implementation-Vendor: Apache Software Foundation
Implementation-URL: http://xml.apache.org/xerces2-j/


Here's the schema:


<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs='http://www.w3.org/2001/XMLSchema'>


       <xs:element name="Zones">
               <xs:complexType>
                       <xs:sequence>
                               <xs:element name="Zone" type="Zone"
maxOccurs="unbounded"/>
                       </xs:sequence>
               </xs:complexType>
               <xs:key name="ZoneName">
                       <xs:selector xpath="./Zone"/>
                       <xs:field xpath="@(protected)"/>
               </xs:key>
               <xs:keyref name="ZoneToZoneName" refer="ZoneName">
                       <xs:selector xpath="./Zone/Zone"/>
                       <xs:field xpath="."/>
               </xs:keyref>
       </xs:element>


       <xs:complexType name="Zone" mixed="true" >
               <xs:choice minOccurs="0" maxOccurs="unbounded">
                       <xs:element name="Country" type="xs:string"/>
                       <xs:element name="Zone" type="Zone"/>
               </xs:choice>
               <xs:attribute name="name" type="xs:string" use="optional"/>

       </xs:complexType>


</xs:schema>


And here's the instance:


<?xml version="1.0" encoding="UTF-8"?>
<Zones>
       <Zone name="United States">
               <Country>US</Country>
       </Zone>


       <Zone name="United States Plus Mexico">
               <Country>MX</Country>
               <Zone>United States</Zone>
       </Zone>
</Zones>


With the keyref I'm validating that the content of the nested zone (in this
case <Zone>United States</Zone>) matches one of the zone names.  Any idea
why this no longer works?


Thanks,
Laura







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


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