[ 
http://issues.apache.org/jira/browse/AXIS-1587?page=comments#action_12317160 ] 

Rodrigo Ruiz commented on AXIS-1587:
------------------------------------

I guess you are right, but at least until java 1.4.2, optional parameters are 
equivalent to nillable ones. In fact, the decision about whether to use the 
direct java type or a wrapper is in the Utils.getParameterTypeName, and there, 
the code is:

if ((parm.isOmittable() && parm.getType().getDimensions().equals(""))
     || parm.getType().getUnderlTypeNillable()) {

  ret = getWrapperType(parm.getType());
}

It seems that isOmittable() is being used as the getUndelTypeNillable() 
equivalent for non-array types.

Thanks,
Rodrigo Ruiz

> WSDL2Java doesn't identify nillable- attributes
> -----------------------------------------------
>
>          Key: AXIS-1587
>          URL: http://issues.apache.org/jira/browse/AXIS-1587
>      Project: Apache Axis
>         Type: Bug
>   Components: WSDL processing
>     Versions: current (nightly)
>  Environment: Axis-1.2-RC1 and all Axis-1.2 releases
>     Reporter: Sami Lakka

>
> WSDL2Java should not bind elements that have nillable- attribute as an 
> primitive value (int etc.) This bug can be fixed by adding
> following lines have into JavaBeanWriter (method preprocess, line 318):
>   
> if (attr.getOptional() || attr.getNillable()) 
>    typeName = Utils.getWrapperType(typeName); 
>  
> The following line have to be added to SchemaUtils (method 
> addAttributeToVector, line 1579):
> attr.setNillable(JavaUtils.isTrueExplicitly(Utils.getAttribute 
> (child,"nillable")));
> Following methods have to be added to ContainedAttribute (or more likely 
> refactored to the ContainedEntry). The boolean attribute nillable has also to 
> be added to ContainedAttribute
>  
>     public void setNillable(boolean nillable) { 
>         this.nillable = nillable; 
>     } 
>     public boolean getNillable() { 
>         return nillable; 
>     } 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to