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.
Resolved: (XERCESJ-1215) Restrictions involving two levels of substitutio

Resolved: (XERCESJ-1215) Restrictions involving two levels of substitutio

2006-11-22       - By Michael Glavassevich (JIRA)

    [ http://issues.apache.org/jira/browse/XERCESJ-1215?page=all ]

Michael Glavassevich resolved XERCESJ-1215.
-------------------------------------------

   Resolution: Duplicate

Duplicate of XERCESJ-1066.

> Restrictions involving two levels of substitution groups raise false errors
> ---------------------------------------------------------------------------
>
>                 Key: XERCESJ-1215
>                 URL: http://issues.apache.org/jira/browse/XERCESJ-1215
>             Project: Xerces2-J
>          Issue Type: Bug
>          Components: XML Schema Structures
>    Affects Versions: 2.8.1
>            Reporter: Eric van der Vlist
>         Attachments: repro1.xsd, repro2.xsd
>
>
> The following schema:
> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
>   <xs:element name="head" type="xs:token"/>
>   <xs:element name="subHead" type="xs:token" substitutionGroup="head"/>
>   <xs:element name="subMember" type="xs:token" substitutionGroup="subHead"/>
>   <xs:complexType name="baseType">
>     <xs:sequence>
>       <xs:element ref="head"/>
>     </xs:sequence>
>   </xs:complexType>
>   <xs:complexType name="restrictionType">
>     <xs:complexContent>
>       <xs:restriction base="baseType">
>         <xs:sequence>
>           <xs:element ref="subHead"/>
>         </xs:sequence>
>       </xs:restriction>
>     </xs:complexContent>
>   </xs:complexType>
> </xs:schema>
> Raises the following errors:
> SystemID: /home/vdv/wadi/repro1.xsd
> Endroit: 21:42
> Description: rcase-RecurseLax.2: There is not a complete functional mapping
between the particles.
> URL: http://www.w3.org/TR/xmlschema-1/#rcase-RecurseLax
> SystemID: /home/vdv/wadi/repro1.xsd
> Endroit: 21:42
> Description: derivation-ok-restriction.5.4.2: Error for type 'restrictionType
'.  The particle of the type is not a valid restriction of the particle of the
base.
> URL: http://www.w3.org/TR/xmlschema-1/#derivation-ok-restriction
> Note that this functionnaly equivalent schema:
> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
>   <xs:element name="head" type="xs:token"/>
>   <xs:element name="subHead" type="xs:token" substitutionGroup="head"/>
>   <xs:element name="subMember" type="xs:token" substitutionGroup="head"/>
>   <xs:complexType name="baseType">
>     <xs:sequence>
>       <xs:element ref="head"/>
>     </xs:sequence>
>   </xs:complexType>
>   <xs:complexType name="restrictionType">
>     <xs:complexContent>
>       <xs:restriction base="baseType">
>         <xs:sequence>
>           <xs:choice>
>             <xs:element ref="subHead"/>
>             <xs:element ref="subMember"/>
>           </xs:choice>
>         </xs:sequence>
>       </xs:restriction>
>     </xs:complexContent>
>   </xs:complexType>
> </xs:schema>
> Is considered valid.
> Thanks,
> Eric

--
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)