Hi Bruno, so far as I can tell, the types are soap types, not the
types on your service portType (interface). We have gone through many
iterations of WSDL generation (sometimes with xsi:type, sometimes
without :-S ) to try to get interop sorted out. What you show many
not actually be wrong. Does the service actually fail? If so, can
you include the entire WSDL and a description of the failure?
Regards, Graham.
> *<tns3:body xsi:type="tns3:tBody" use="literal"/>*
> </input>
> <output>
> *<tns3:body xsi:type="tns3:tBody" use="literal"/>*
> </output>
> <tns3:operation xsi:type="tns3:tOperation" soapAction=""/>
> </operation>
> <tns3:binding xsi:type="tns3:tBinding"
> transport="
http://schemas.xmlsoap.org/soap/http"
> style="document"/>
> </binding>
>
> I get:
>
> <wsdl:binding name="WeatherServiceBinding"
> type="tns2:WeatherServicePortType">
> <soap:binding transport="
http://schemas.xmlsoap.org/soap/http"
> style="document"/>
> -
> <wsdl:operation name="getTemperature">
> <soap:operation soapAction=""/>
> -
> *<wsdl:input>
> <soap:body use="literal"/>
> </wsdl:input>
> -
> <wsdl:output>
> <soap:body use="literal"/>
> </wsdl:output>*