[
https://issues.apache.org/jira/browse/XERCESJ-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476857#comment-13476857
]
Mukul Gandhi commented on XERCESJ-1579:
---------------------------------------
@ Octavian : wrt your example, if I specify the complex type definitions as
following:
<xsd:complexType name="base">
<xsd:choice>
<xsd:element name="e1" minOccurs="0" maxOccurs="1000000000"/>
<xsd:element name="e2" minOccurs="0" maxOccurs="1000000000"/>
</xsd:choice>
</xsd:complexType>
<xsd:complexType name="testing">
<xsd:complexContent>
<xsd:restriction base="x:base">
<xsd:choice>
<xsd:element name="e1" minOccurs="1" maxOccurs="9999999"/>
<xsd:element name="e2" minOccurs="1" maxOccurs="9999999"/>
</xsd:choice>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
I don't get the errors that you've cited, and get an instant result. I've
changed the value of "maxOccurs" from 'unbounded' to a very large number like
1000000000, in the base type. The value of "maxOccurs" in the derived type is
still same.
Remember, that the XSD specification refers to infinite cardinalities as
"countably infinite" (for e.g, a value space of xs:integer. I suspect, this
means a very large set that can be practically represented using available
computing resources, but which are theoretically infinite).
I therefore think, we do comply to the XSD spec (1.0 and 1.1 both) wrt the use
case provided in this bug report. Perhaps, an attribute of this bug report may
be changed to improvement/wish.
> Possible infinite loop while validating a schema that contains complex type
> restrictions
> ----------------------------------------------------------------------------------------
>
> Key: XERCESJ-1579
> URL: https://issues.apache.org/jira/browse/XERCESJ-1579
> Project: Xerces2-J
> Issue Type: Bug
> Components: XML Schema 1.1 Structures
> Reporter: Octavian Nadolu
> Priority: Critical
>
> There seems to be an infinite loop while validating the schema with "full
> schema checking" and XML Schema 1.1 features, on the xml-schema-1.1-dev
> branch.
> You can reproduce the issue on the xml-schema-1.1-dev branch, using the
> jaxp.SourceValidator as follows:
> jaxp.SourceValidator -xsd11 -f -a particlesIe003.xsd
> Schema: particlesIe003.xsd
> {code}
> <?xml version="1.0"?>
> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> targetNamespace="http://xsdtesting"; xmlns:x="http://xsdtesting";
> elementFormDefault="qualified">
> <xsd:complexType name="base">
> <xsd:choice>
> <xsd:element name="e1" minOccurs="0"
> maxOccurs="unbounded"/>
> <xsd:element name="e2" minOccurs="0"
> maxOccurs="unbounded"/>
> </xsd:choice>
> </xsd:complexType>
> <xsd:complexType name="testing">
> <xsd:complexContent>
> <xsd:restriction base="x:base">
> <xsd:choice>
> <xsd:element name="e1" minOccurs="1"
> maxOccurs="9999999"/>
> <xsd:element name="e2" minOccurs="1"
> maxOccurs="9999999"/>
> </xsd:choice>
> </xsd:restriction>
> </xsd:complexContent>
> </xsd:complexType>
> <xsd:element name="doc" type="x:testing"/>
> </xsd:schema>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
