You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-dev@axis.apache.org by bu...@apache.org on 2003/07/09 02:39:05 UTC

DO NOT REPLY [Bug 20109] - WSDL2Java "soapenc" instead of "xsd" for boolean and long

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20109>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20109

WSDL2Java "soapenc" instead of "xsd" for boolean and long





------- Additional Comments From d_axis@axonchisel.net  2003-07-09 00:39 -------
Ah, to clarify this bug as it is a bit more specific than indicated:  This 
problem only happens with xsd:longs which are explicitly marked as 
nillable=true !

So this works fine (WSDL2Java output proper code in xsd ns):
  <element name="eyes" type="xsd:long"/>

but this doesn't (WSDL2Java outputs soapenc ns metadata in field desc):
  <element name="eyes" nillable="true" type="xsd:long"/>

And note that this incorrect output happens even with document/literal style, 
which in a large part is about getting away from soap encoding entirely.