2 Replies Latest reply on Aug 23, 2007 11:44 AM by GG

    .Net parameter interoperabilty

    Joe Kemp Newbie

      We have been trying to fix this problem for .Net clients. The java2wsdl generated file has the parameters as a element that references a complex type. Unfortunately the proxy classes .Net creates interprets this as a separate object that needs to be passed into the method. .Net seems to want the element tag to wrap the type definition. Otherwise it sticks in this extra object as the parameter. Is there a easy way to control the way java2wsdl creates the wsdl file? I have examples below of both formats.

      java2wsdl format:








      Desired .Net friendly format:









      Our WebSphere servers are creating the ".Net Friendly" format but they are probably built on an earlier version of axis.

        • 1. Re: .Net parameter interoperabilty
          Joe Kemp Newbie

          The XML did not stick

          java2wsdl format:

          <complexType name="getPerson">
           <sequence>
           <element name="String_1" nillable="true" type="string"/>
           <element name="String_2" nillable="true" type="string"/>
           </sequence>
          </complexType>
          <element name="getPerson" type="tns:getPerson"/>
          
          Desired .Net friendly format:
          <element name="getPerson">
           <complexType>
           <sequence>
           <element name="String_1" nillable="true" type="string"/>
           <element name="String_2" nillable="true" type="string"/>
           </sequence>
           </complexType>
          </element>
          



          • 2. Re: .Net parameter interoperabilty
            GG Newbie

            Using @XmlRootElement + @XmlType(name="") helps?