[ 
https://issues.apache.org/jira/browse/XERCESJ-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801397#comment-13801397
 ] 

Mukul Gandhi commented on XERCESJ-1615:
---------------------------------------

I agree that as per our current resolution so far for this bug, this new use 
case should be dealt similarly.

But I don't think, we should generalize the current solution (which requires 
detecting this situation during schema XML representation traversal) to all the 
way up the XSD type hierarchy.

Also this is correctly handled just now during XSD component construction 
(which actually affects validation behavior), as prescribed by the XSD spec.

> Error not reported on duplicate attributes
> ------------------------------------------
>
>                 Key: XERCESJ-1615
>                 URL: https://issues.apache.org/jira/browse/XERCESJ-1615
>             Project: Xerces2-J
>          Issue Type: Bug
>          Components: XML Schema 1.0 Structures, XML Schema 1.1 Structures
>    Affects Versions: 2.11.0
>            Reporter: Octavian Nadolu
>            Assignee: Mukul Gandhi
>
> If I validate the following schema Xerces does not complain about the the 
> duplicate attribute. The same attribute group is referred twice.
> You can reproduce the issue on the xml-schema-1.1-dev branch.
> -------- schema.xsd --------------------
> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
> elementFormDefault="qualified">
>     <xs:complexType name="baseType">
>         <xs:attributeGroup ref="globalAttributes"/>
>         <xs:attributeGroup ref="globalAttributes"/>
>     </xs:complexType>
>     
>     <xs:attributeGroup name="globalAttributes">
>         <xs:attribute name="id" type="xs:ID"/>
>     </xs:attributeGroup>
> </xs:schema>
> -------------------------------------------------------



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to