axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <>
Subject [jira] Resolved: (AXIS2-998) WSDL2Java creates invalid databinding code for choice elements with maxOccurs="unbounded"
Date Thu, 10 Aug 2006 05:42:14 GMT
     [ ]

Davanum Srinivas resolved AXIS2-998.

    Resolution: Fixed

Turned out to be a problem in XmlSchema parser. Fixed in svn revision 430259.

-- dims

> WSDL2Java creates invalid databinding code for choice elements with maxOccurs="unbounded"
> -----------------------------------------------------------------------------------------
>                 Key: AXIS2-998
>                 URL:
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: wsdl, databinding, Tools
>    Affects Versions: 1.0
>         Environment: Windows XP
>            Reporter: Barney Wrightson
>         Attachments: testChoice.wsdl
> When generating code from a wsdl file that uses a choice element with maxOccurs="unbounded"
the resulting code appears to have ignored the maxOccurs specification. I am using the xmlbeans
method, and if i try to validate xml based on the wsdl schema it oly accepts it if there is
only one of the choice elements used.
> eg. for the attached example wsdl, if i send a call NewOperation with something like
the the following as input, validation fails on the <intChoice>:
> <NewOperationRequest >
>   <stringChoice>string</stringChoice>
>   <intChoice>1</intChoice>
> </NewOperationRequest >
> In the generated code the NewOperationRequestDocument returns a single MultipleChoice
object in the getNewOperationRequest method, and MultpleChoice has all possible options in
it but there are no arrays anywhere in there either.
> I have tried to work around this issue in the shema definition, but apart from adding
superfluous elements, which changes the structure of the xml, nothing works. eg. Putting the
choice element as maxOccurs="1" inside a sequence with maxOccurs="unbounded" yeilds identical
> According to this email to the axis-user list, the required functionality was present
at version 0.94 or so and has been subsequently left out:

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message