java2wsdl generates wrong WSDL for java.lang.Boolean operation parameters
-------------------------------------------------------------------------
Key: AXIS-2366
URL: http://issues.apache.org/jira/browse/AXIS-2366
Project: Apache Axis
Type: Bug
Components: WSDL processing
Versions: 1.3
Environment: Windows XP Pro, Java 1.5
Reporter: Jarmo Doc
Axis 1.3 is bugged in two places, once in java2wsdl and once in wsdl2java). If
you write a doc/lit service that contains a service operation such as public
void update(Employee [] employees, Boolean sacked) then:
1. java2wsdl does not generate nillable="true" for 'sacked' when it should, and
2. even if you manually add nillable="true" to the WSDL for 'sacked', wsdl2java
does not generate Boolean, instead it generates boolean
Note that java2wsdl does work correctly for java.lang.Boolean in a user-defined
class (e.g. Employee) but not when explicilty as a parameter to the service
operation itself. Consequently the generated WSDL is wrong and clients are
restricted to using intrinsic boolean types which can only have value
true/false rather than true/false/null.
One workaround is to manually edit the WSDL and add minOccurs="0" maxOccurs="1"
in which case wsdl2java does correctly generate the client stub (as does the
gSOAP wsdl2h equivalent).
--
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
