DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5196>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5196

False multiple identity constraints

           Summary: False multiple identity constraints
           Product: Xerces-J
           Version: 1.4.4
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Schema-Structures
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


Xerces report this error: (for a Schema where the identity constrain XXXX only 
appears once) 
Schema Error: More than one identity constrain named XXXX

I have asked the question in XMLSCHEMA-DEV mailing list of W3C, to know if 
my schema is invalid or it's a Xerces bug. And they say my that my schema 
looks good. And the error is probably a Xerces bug.

This is the most minimized schema that I can construct to reproduce the error.
I couldn't discover the nature of the error, and reproduce it in a shorter 
schema.
For example if you delete the unique constraint of the Scalar element the error
dosn't appears. Its strange...

    <group name="GElementType">
        <choice>
            <element name="Struct" type="spe:TStruct">
                <unique name="NameStruct">
                    <selector xpath="*"/>
                    <field xpath="@name"/>
                </unique>
            </element>
            <element name="Scalar" type="spe:TScalar">
                <unique name="NameScalar">
                    <selector xpath="Attribute"/>
                    <field xpath="@name"/>
                </unique>
            </element>
        </choice>
    </group>

    <complexType name="TStruct">
        <choice maxOccurs="unbounded">
            <group ref="spe:GElementType"/>
        </choice>
        <attribute name="name" type="NCName" use="required"/>
    </complexType>

    <complexType name="TScalar">
        <attribute name="name" type="NCName" use="required"/>
    </complexType>

PS1:You can see the discusion in W3C schema list here:
http://lists.w3.org/Archives/Public/xmlschema-dev/2001Nov/0260.html

PS2: In the Scalar unique contraints appears an inexistent Attribute element in 
the xpath. I don't include it to not enlarge the example.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to