Hi,

after additional experiments, it seems that the described problem appears for 
primitives inside container types, but not for primitives that are directly 
exposed on the interface. For example, a boolean with the WSDL attributes 
nillable="false" and minOccurs="1" results in a primitive type (after 
WSDL2Java) if it is an immediate input or output value of a function. However, 
if it is contained in some other object, the wrapper type Boolean is generated. 
Candidate for a Jira issue?

Regards,
Nenad Jovanovic

> Hi all,
> 
> the -Euwc option (introduced in 
> https://issues.apache.org/jira/browse/AXIS2-3353) of 
> org.apache.axis2.wsdl.WSDL2Java generates wrappers for nillable 
> (nillable="true") or optional (minOccurs="0") elements. However, it also 
> generates wrappers for types that are neither nillable nor optional. Is this 
> behavior intended? For details, see below.
> 
> Thanks,
> Nenad Jovanovic
> 
> 
> WSDL snippet:
> 
>     <xs:complexType name="Container">
>         <xs:sequence>
>             <!-- java.lang.Boolean will be used for all the following 
> elements; expected for myBoolean4: primitive type "boolean" -->
>             <xs:element minOccurs="0" nillable="true" name="myBoolean1" 
> type="xs:boolean"/>
>             <xs:element minOccurs="0" nillable="false" name="myBoolean2" 
> type="xs:boolean"/>
>             <xs:element minOccurs="1" nillable="true" name="myBoolean3" 
> type="xs:boolean"/>
>             <xs:element minOccurs="1" nillable="false" name="myBoolean4" 
> type="xs:boolean"/>
>         </xs:sequence>
>     </xs:complexType>
>
> Code generation parameters in the Ant buildfile:
>
>         <arg line="-uri ${wsdl.uri}"/>
>         <arg line="-o ${build.dir}/service"/>
>         <arg line="-ss"/>
>         <arg line="-sd"/>
>         <arg line="-s"/>
>         <arg line="-Euwc"/>
>         <arg line="-Eosv"/>
>         <arg line="-ssi"/>
>         <arg line="-uw"/>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to