Mailing-List: contact c-dev-help@xerces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: c-dev@xerces.apache.org
Message-ID: <13340168.1156861944413.JavaMail.jira@brutus>
Date: Tue, 29 Aug 2006 07:32:24 -0700 (PDT)
From: "Alberto Massari (JIRA)" <xerces-c-dev@xml.apache.org>
To: c-dev@xerces.apache.org
Subject: [jira] Commented: (XERCESC-1627) Schema validator sensitive to the
 order of xsd:import and xsd:include elements.
In-Reply-To: <28910404.1156841730934.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/XERCESC-1627?page=comments#action_12431253 ] 
            
Alberto Massari commented on XERCESC-1627:
------------------------------------------

Please download and test the latest version of Xerces (1.7 is very old,the latest is 2.7); also, attach the XMLSchema involved.

> Schema validator sensitive to the order of xsd:import and xsd:include elements.
> -------------------------------------------------------------------------------
>
>                 Key: XERCESC-1627
>                 URL: http://issues.apache.org/jira/browse/XERCESC-1627
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: Validating Parser (Schema) (Xerces 1.5 or up only)
>    Affects Versions: 1.5, 1.6.0, 1.7.0
>         Environment: Windows XP SR2
>            Reporter: Peter Aberline
>            Priority: Minor
>         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.
-
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: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org