Web Service Interoperability - Java SOA - page 801

<wsdl:output name="HelloMsg">
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="GreetingServiceSoap12"
type="tns:GreetingServiceSoap">
<soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
<wsdl:operation name="niceGreeting">
<soap12:operation soapAction="http://soacookbook.com/dotnet/
HelloMsg"
style="document" />
<wsdl:input name="HelloMsg">
<soap12:body use="literal" />
</wsdl:input>
<wsdl:output name="HelloMsg">
<soap12:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="GreetingService">
<wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
Returns greetings.
</wsdl:documentation>
<wsdl:port name="GreetingServiceSoap"
binding="tns:GreetingServiceSoap">
<soap:address location="http://localhost:3416/WebSite1/
Service.asmx" />
</wsdl:port>
<wsdl:port name="GreetingServiceSoap12"
binding="tns:GreetingServiceSoap12">
<soap12:address location="http://localhost:3416/WebSite1/
Service.asmx" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
You can see that the WSDL generated by .NET Framework 2.0 is very different from that
generated by Java EE 5, but many strides have been made in recent years to ensure interop-
erability between the Java and .NET platforms. Some of the changes are little more than cos-
metic, but some offer different features. To begin with, the ASP.NET-generated WSDL allows
you to invoke the service over SOAP 1.1 or SOAP 1.2. There are two binding entries in the
wsdl:service element, one for each portType , bound to the same address.