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.
Created: (XERCESJ-1139) Validation of an optional substituted element in

Created: (XERCESJ-1139) Validation of an optional substituted element in

2006-02-24       - By Martin Thomson (JIRA)

Validation of an optional substituted element in a restriction fails
--------------------------------------------------------------------

        Key: XERCESJ-1139
        URL: http://issues.apache.org/jira/browse/XERCESJ-1139
    Project: Xerces2-J
       Type: Bug
 Components: XML Schema Structures  
   Versions: 2.7.1    
Environment: Java [1.]5
   Reporter: Martin Thomson


Xerces fails to validate when an optional element is replaced by one in its
substitution group in a restriction.  With a standalone element, this fails
with the claim that there is not a complete mapping between particles.

That is, where X2 is a restriction of X1 and Y2 is substitutable for Y1, the
following results in the rcase-RecurseLax.2 error:

X1 = (Y1?)
X2 = (Y2?)

The following also causes a rcase-Recurse.2 error:

X1 = (Y1?, Z)
X2 = (Y2?, Z)

The following are accepted:

X2 = (Y1?)
X2 = (Y2)

However, if I add Y3 (substitutable for Y2), the last also fails.

XSV (http://www.w3.org/2001/03/webdata/xsv) validates the schema successfully.

The only related issues I could find were XERCESJ-1066 (yes, mine) and XERCESJ
-922, but I think that those are different.  Although, like these issues, I
think that this is related to the way that choices are introduced and
subsequently collapsed.


-- Test Schema
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
           targetNamespace="urn:subs" xmlns="urn:subs"
           xmlns:subs="urn:subs"
           elementFormDefault="qualified">

 <xsd:element name="Y1" type="xsd:anyType"/>
 <xsd:element name="Y2" type="xsd:anyType" substitutionGroup="Y1"/>
 <xsd:element name="Y3" type="xsd:anyType" substitutionGroup="Y2"/>

 <xsd:element name="X1" type="x1"/>
 <xsd:complexType name="x1">
   <xsd:complexContent>
     <xsd:restriction base="xsd:anyType">
       <xsd:sequence>
         <xsd:element ref="Y1" minOccurs="0"/>
       </xsd:sequence>
     </xsd:restriction>
   </xsd:complexContent>
 </xsd:complexType>

 <!-- Xerces Error -->
 <xsd:element name="X2-a" type="x2-a"/>
 <xsd:complexType name="x2-a">
   <xsd:complexContent>
     <xsd:restriction base="x1">
       <xsd:sequence>
         <xsd:element ref="Y2" minOccurs="0"/>
       </xsd:sequence>
     </xsd:restriction>
   </xsd:complexContent>
 </xsd:complexType>

 <xsd:element name="X2-b" type="x2-b"/>
 <xsd:complexType name="x2-b">
   <xsd:complexContent>
     <xsd:restriction base="x1">
       <xsd:sequence>
         <xsd:element ref="Y1" minOccurs="0"/>
       </xsd:sequence>
     </xsd:restriction>
   </xsd:complexContent>
 </xsd:complexType>

 <!-- Xerces Error -->
 <xsd:element name="X2-c" type="x2-c"/>
 <xsd:complexType name="x2-c">
   <xsd:complexContent>
     <xsd:restriction base="x1">
       <xsd:sequence>
         <xsd:element ref="Y2"/>
       </xsd:sequence>
     </xsd:restriction>
   </xsd:complexContent>
 </xsd:complexType>

 <xsd:element name="X2-d" type="x2-d"/>
 <xsd:complexType name="x2-d">
   <xsd:complexContent>
     <xsd:restriction base="x1">
       <xsd:sequence>
         <xsd:element ref="Y3"/>
       </xsd:sequence>
     </xsd:restriction>
   </xsd:complexContent>
 </xsd:complexType>

</xsd:schema>


--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
  http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
  http://www.atlassian.com/software/jira


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