DO NOT REPLY [Bug 9848] New: - Compatibility problems between AXIS and WASP

[bugzilla]

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=9848>.
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=9848

Compatibility problems between AXIS and WASP

           Summary: Compatibility problems between AXIS and WASP
           Product: Axis
           Version: current (nightly)
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Basic Architecture
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


We are building a web services architecture. We want to deploy our services to 
Systinet WASP. Our developers use the IntelliJ IDE, and we have built a plug-in 
for IntelliJ that generates stubs from WSDL files using Apache AXIS. Problem: 
the wsdl files generated by the WASP deployment tool are not completely 
compatible with AXIS. Here is an example:

--------------------------------------------------------------------------

** wsdl generated by WASP Java2Wsdl:

<xsd:schema 
targetNamespace="http://idoox.com/wasp/tools/java2wsdl/output/demo/types/service
/">
        <xsd:complexType name="ArrayOfint">
                <xsd:complexContent>
                        <xsd:restriction base="SOAP-ENC:Array">
                                <xsd:sequence>
                                        <xsd:element name="item" 
type="xsd:int" /> 
                                </xsd:sequence>
                                <xsd:attribute ref="SOAP-ENC:arrayType" 
wsdl:arrayType="xsd:int[]" /> 
                        </xsd:restriction>
        </xsd:complexContent>
  </xsd:complexType>
</xsd:schema>

** wsdl generated by AXIS Java2Wsdl:

<schema xmlns="http://www.w3.org/2001/XMLSchema"; 
targetNamespace="urn:echoTypes">
        <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
        <complexType name="ArrayOf_xsd_int">
        <complexContent>
                <restriction base="SOAP-ENC:Array">
                <attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="xsd:int[]"/>
                </restriction>
        </complexContent>
        </complexType>
  <element name="ArrayOf_xsd_int" nillable="true" type="intf:ArrayOf_xsd_int"/>
</schema>

** Code generated by AXIS Wsdl2Java:

package echo;

public class ArrayOfint  implements java.io.Serializable {
    public ArrayOfint() {
    }

    private Object __equalsCalc = null;
    public synchronized boolean equals(Object obj) {
        if (!(obj instanceof ArrayOfint)) return false;
        ArrayOfint other = (ArrayOfint) obj;
        if (obj == null) return false;
        if (this == obj) return true;
        if (__equalsCalc != null) {
            return (__equalsCalc == obj);
        }
        __equalsCalc = obj;
        boolean _equals;
        _equals = true;
        __equalsCalc = null;
        return _equals;
    }

    private boolean __hashCodeCalc = false;
    public synchronized int hashCode() {
        if (__hashCodeCalc) {
            return 0;
        }
        __hashCodeCalc = true;
        int _hashCode = 1;
        __hashCodeCalc = false;
        return _hashCode;
    }

    /**
     * Get Custom Serializer
     */
    public static org.apache.axis.encoding.Serializer getSerializer(
           String mechType, 
           Class _javaType,  
           javax.xml.namespace.QName _xmlType) {
        return 
          new  org.apache.axis.encoding.ser.BeanSerializer(
            _javaType, _xmlType, null);
    }

    /**
     * Get Custom Deserializer
     */
    public static org.apache.axis.encoding.Deserializer getDeserializer(
           String mechType, 
           Class _javaType,  
           javax.xml.namespace.QName _xmlType) {
        return 
          new  org.apache.axis.encoding.ser.BeanDeserializer(
            _javaType, _xmlType, null);
    }
}

------------------------------------------------------------------

As you can see, the generated code is worthless, as there is no int field. Is 
this a problem with AXIS, a problem with WASP, both, or neither? It seems a 
very real possibility that someone might want to use AXIS to consume services 
published using WASP or a different deployment tool. Shouldn't AXIS handle this?