[jira] Updated: (XERCESJ-1238) Reference to "all" model group allows maxOccurs > 1

["Michael Glavassevich (JIRA)" <xe...@xml.apache.org>]

     [ https://issues.apache.org/jira/browse/XERCESJ-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Glavassevich updated XERCESJ-1238:
------------------------------------------

    Fix Version/s: 2.9.1

> Reference to "all" model group allows maxOccurs > 1
> ---------------------------------------------------
>
>                 Key: XERCESJ-1238
>                 URL: https://issues.apache.org/jira/browse/XERCESJ-1238
>             Project: Xerces2-J
>          Issue Type: Bug
>          Components: XML Schema Structures
>    Affects Versions: 2.9.0
>            Reporter: Michael Glavassevich
>            Assignee: Michael Glavassevich
>             Fix For: 2.9.1
>
>
> The XML Schema spec [1] states that if the {term} property of a particle is a model group with {compositor} all then {maxOccurs} of that particle must equal 1. Xerces currently allows maxOccurs > 1 for references to a model group definition whose model group has {compositor} all, for instance:
> <xs:group name="myGroup">
>  <xs:all>
>   <xs:element name="a"/>
>   <xs:element name="b"/>
>   <xs:element name="c"/>
>  </xs:all>
> </xs:group>
> <xsd:complexType name="myInvalidType">
>  <xsd:group ref="myGroup" maxOccurs="100">
> </xsd:complexType>
> This bug is causing one test in the W3C XML Schema 1.0 2nd Edition test suite to fail:
> msData/particles/particlesEa025.xsd
> [1] http://www.w3.org/TR/xmlschema-1/#cos-all-limited

-- 
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: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org