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

[bu...@apache.org]

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

           Summary: WSDL2Java "soapenc" instead of "xsd" for boolean and
                    long
           Product: Axis
           Version: 1.0-rc1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Serialization/Deserialization
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: dbkdb@hotmail.com


This problem has been around for as long as I can remember.  Basically: 

A WSDL file has "xsd:long" or "xsd:boolean" types in it.  WSDL2Java generates 
Java code for the TypeDesc with the "soapenc" ( 
http://schemas.xmlsoap.org/soap/encoding/ ) namespace instead of xsd ( 
http://www.w3.org/2001/XMLSchema ) namespace.

Thus output XML is incorrect (in contradiction to WSDL) and server may have 
parse errors handling xsd types when it is trying to read soapencs.

This was described along with sample code in the mailing list many months ago:
  http://marc.theaimsgroup.com/?l=axis-user&m=104819287804565&w=2

Please fix this, as it makes interop very difficult and painful.  I'm not sure 
how this has not been noticed for so long, but perhaps people aren't using 
booleans and longs?