<element name="X" type="Y"/> where this one is
<element name="X" ref="Z"/>
Could you try your scenario with a type instead of a referenced element to see if that works?
Also, could you open a bug with bugzilla? http://nagoya.apache.org/bugzilla/index.html There are more and more axis-users and almost no increase in active axis committers, so we often lose track of axis-user. Reporting the bug through bugzilla ensures that we will look at it eventually.
Russell Butek
[EMAIL PROTECTED]
Please respond to [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
cc:
Subject: Re: wsdl2java bug?
Seems to be a bug. I discovered the same.
Nobody on this list answered my question
about that.
Regards
Dennis Reil
----- Original Message -----
From: "Tolsch, Ed" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 05, 2002 11:19 PM
Subject: wsdl2java bug?
> I'm wondering if the wsdl2java has a bug or I'm doing something wrong.
>
> 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()
> }
>
> I would have expected to see the variable participantLifeEvent defined as
> some type of Vector since it is unbounded in the WSDL? A Participant can
> have multiple ParticipantLifeEvents.
> Is this a bug or am I missing something?
>
> Ed Tolsch
> [EMAIL PROTECTED]
>
