[ http://issues.apache.org/jira/browse/JAXME-63?page=all ]
Jochen Wiedmann updated JAXME-63: --------------------------------- Attachment: JAXME63.patch Patch for the problem. > JaxMe (wrongly) accepts schema using <group ref="..." maxOccurs="unbounded"/> > ----------------------------------------------------------------------------- > > Key: JAXME-63 > URL: http://issues.apache.org/jira/browse/JAXME-63 > Project: JaxMe > Type: Bug > Components: JaxMe Core > Versions: current (nightly) > Environment: JDK 1.5.0, JaxMe CVS > Reporter: Fredrik Vraalsen > Fix For: 0.5 > Attachments: JAXME63.patch > > 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? -- 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]