Thanks Alex, That worked!
-----Original Message----- From: Alex Huang [mailto:alex.huang@;openwave.com] Sent: Saturday, October 19, 2002 3:24 PM To: [EMAIL PROTECTED] Subject: RE: wsdl2Java - an observation I don't know if that's a bug. I've used named complexType and maxOccurs="unbounded" and that works so you can use that as the work around. <complexType name="ItemType"> ... </compexType> <element name="Item" type="ItemType" maxOccurs="unbounded"/> --Alex > -----Original Message----- > From: Naveen Srinivasa Murthy [mailto:nmurthy@;datalinx.net] > Sent: Friday, October 18, 2002 11:58 AM > To: [EMAIL PROTECTED] > Subject: wsdl2Java - an observation > Importance: High > > > > I have a wsdl in which one of my input params to the webservice is > defined as a 'complexType' (a schema is attached with > the wsdl.) (the message part 'arg' is of type ''shiporder") > > When I run my wsdl2Java against the WSDL URL, it does > successfully generate the java classes. It has also > generated a Shiporder java object for me. But even though > the schema tells that "a shiporder may contains 'unbounded' > number of 'item's ", the wsdl2Java generated Shiporder class > has only one 'Item' object. > > Is this a wsdl2java bug? or am I missing something? > > Im attaching the wsdl, and the shiporder java object for ur > reference. > > thanks > Naveen > >
