The parser do no support multiple inclusions of the same "sub"-schema
---------------------------------------------------------------------

         Key: XERCESJ-1112
         URL: http://issues.apache.org/jira/browse/XERCESJ-1112
     Project: Xerces2-J
        Type: Bug
  Components: XML Schema Structures  
    Versions: 2.7.1    
 Environment: Any platform. Problem exists on any version of Xerces
    Reporter: Jean-Jacques Thomasson


An example :

In a schema named "complexTypes.xsd", we define the following inclusions :
        <xs:include schemaLocation="attributeGroups.xsd"/>
        <xs:include schemaLocation="simpleElements.xsd"/>
        <xs:include schemaLocation="complexElements.xsd"/>
        <xs:include schemaLocation="elementGroups.xsd"/>

and, in "complexEelements.xsd", we use the following inclusions :
        <xs:include schemaLocation="complexTypes.xsd"/>

(Since we need element definitions to define complexTypes and vice-versa).

Most of the parsers (XSV, XMLSpy) are now supporting this kind of 
self-mirroring inclusions  which is admitted by the W3C recommendation (Note 2 
of section 4.2.1 "Schema Representation Constraint: Inclusion Constraints and 
Semantics ").

But Xerces produces (a series of) the following sample message :
"[Error] complexTypes.xsd:32:54: sch-props-correct.2: A schema cannot contain 
two global components with the same name; this schema contains two occurrences 
of ',contentType_fn3dktizrknc9pi'."

It is an important matter of concern for industries wishinig to have a complex 
architecture of schemas such as the aeerospace industry.

Please, could you look at this ?

Jean-Jacques Thomasson
 

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to