Looks like the minOccurs/maxOccurs DOES work in WSDL2Java when you have elements of the form:
<element name="X" type="Y" minOccurs=0 maxOccurs="unbounded"/> But they DO NOT appear to work with elements of the form: <element ref="Z" minOccurs=0 maxOccurs="unbounded"/> I'm changing my schema to use the above definition. Hope this helps. -----Original Message----- From: Dennis Reil [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 8:32 AM To: Tolsch, Ed Subject: Re: wsdl2java bug? I just posted a reply to the list. Seems to be a bug of the tool. It's very annoying. Nobody answered my question about that and I didn't find a solution for that problem. Regards Dennis Reil ----- Original Message ----- From: "Tolsch, Ed" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, June 06, 2002 3:24 PM Subject: wsdl2java bug? > HI, > I noticed your posting on the axis news group about the > minOccurs/maxOccurs not being interrogated by wsdl2java; therefor my > generated beans are not correct in that they can only accept one bean and > not an array of beans. > > Did you ever find an answer to this? Thanks in advance. > > I recently posted the exact same question before finding your post (below) > > I have the following within my WSDL file: > > . . . > <xsd0:element name="Participant"> > <xsd0:complexType> > <xsd0:sequence> > <xsd0:element > ref="xsd1:ParticipantLifeEvent" minOccurs="0" maxOccurs="unbounded"/> > </xsd0:sequence> > <xsd0:attribute name="transaction" > type="xsd0:string" use="optional"/> > </xsd0:complexType> > </xsd0:element> > . . . > > When I run wsdl2java, the bean which gets generated looks like the > following: > > public class Participant implements java.io.Serializable > { > . . . > private com.fmr.fesco.hw.axis.ParticipantLifeEvent participantLifeEvent; > > getters() > setters() > } > > Ed Tolsch > 817.474.9939 > [EMAIL PROTECTED] >
