You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by "Boris Kolpackov (JIRA)" <xe...@xml.apache.org> on 2009/11/18 09:10:39 UTC
[jira] Closed: (XERCESC-1627) Schema validator sensitive to the
order of xsd:import and xsd:include elements.
[ https://issues.apache.org/jira/browse/XERCESC-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Kolpackov closed XERCESC-1627.
------------------------------------
Resolution: Fixed
Fix Version/s: 3.1.0
With the multiple import enabled, I get the same output with the original schema and with the swapped include/import. There are some other schema and validation errors but I am assuming the original bug is fixed.
> Schema validator sensitive to the order of xsd:import and xsd:include elements.
> -------------------------------------------------------------------------------
>
> Key: XERCESC-1627
> URL: https://issues.apache.org/jira/browse/XERCESC-1627
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 2.5.0, 2.6.0, 2.7.0
> Environment: Windows XP SR2
> Reporter: Peter Aberline
> Priority: Minor
> Fix For: 3.1.0
>
> Attachments: schema_validator_bug.zip
>
>
> Xerces validating schema parser appears to be intolerant of the order of xsd:import and xsd:include elements.
> This can be demonstrated with the the DOMCount program:
> DOMCount -s -n -v=always CSW_caps.xml
> This causes validation errors by the schema validator unable to resolve types included in owsGetCapabilities. Swapping the order of the
> <xsd:include> to after the <xsd:import> (lines 22-25 of CSW-discovery.xsd) solves the validation error.
> The fragment of XMLSchema.xsd shown below suggests to me that import and include elements can be in any order?
> http://www.w3.org/2001/XMLSchema.xsd:
> <xs:element name="schema" id="schema">
> <xs:annotation>
> <xs:documentation source="http://www.w3.org/TR/xmlschema-1/#element-schema"/>
> </xs:annotation>
> <xs:complexType>
> <xs:complexContent>
> <xs:extension base="xs:openAttrs">
> <xs:sequence>
> <xs:choice minOccurs="0" maxOccurs="unbounded">
> <xs:element ref="xs:include"/>
> <xs:element ref="xs:import"/>
> <xs:element ref="xs:redefine"/>
> <xs:element ref="xs:annotation"/>
> </xs:choice>
> <xs:sequence minOccurs="0" maxOccurs="unbounded">
> <xs:group ref="xs:schemaTop"/>
> <xs:element ref="xs:annotation" minOccurs="0" maxOccurs="unbounded"/>
> </xs:sequence>
> ...
> ...
> </xs:sequence>
> </xs:extension>
> </xs:complexContent>
> </xs:complexType>
> </xs:element>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org