[JAXME-63] JaxMe (wrongly) accepts schema using <group ref="..." maxOccurs="unbounded"/>

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: current (nightly)
• Fix Version/s: 0.5
• Component/s: JaxMe Core
• Environment: JDK 1.5.0, JaxMe CVS
• Assignee: Jochen Wiedmann
• Reporter: Fredrik Vraalsen
• Created: 04/Aug/05 22:18
• Updated: 05/Aug/05 06:29
• Resolved: 05/Aug/05 06:29

Description

JaxMe accepts (and generates faulty code for) the following schema:

<xs:group name="params">
<xs:choice>
<xs:element name="string" type="xs:string"/>
<xs:element name="int" type="xs:int"/>
<xs:element name="boolean" type="xs:boolean"/>
</xs:choice>
</xs:group>

<xs:element name="call">
<xs:complexType>
<xs:group ref="params" maxOccurs="unbounded"/>
</xs:complexType>
</xs:element>

However, it should give an error message about not supporting model groups with maxOccurs > 1, as it does with the following schema:

<xs:element name="call">
<xs:complexType>
<xs:choice maxOccurs="unbounded">
<xs:element name="string" type="xs:string"/>
<xs:element name="int" type="xs:int"/>
<xs:element name="boolean" type="xs:boolean"/>
</xs:choice>
</xs:complexType>
</xs:element>

Perhaps somewhat related to JAXME-61, but I think the correct behaviour would be to fail with an error message on the first schema above until support for groups with maxOccurs > 1 is working?