Okay, I found where the difference of soap and soap12, which I hadn't noticed before. However, I don't see anything defining a difference between the two.
<wsdl:binding name="MessageServiceSoap11Binding" type="ns:MessageServicePortType"> <soap:binding transport="http://schemas.xmlsoap.org/soap/http"; style="document"/> − <wsdl:operation name="sendMessages"> <soap:operation soapAction="urn:sendMessages" style="document"/> − <wsdl:input> <soap:body use="literal"/> </wsdl:input> </wsdl:operation> − <wsdl:operation name="getMessages"> <soap:operation soapAction="urn:getMessages" style="document"/> − <wsdl:input> <soap:body use="literal"/> </wsdl:input> − <wsdl:output> <soap:body use="literal"/> </wsdl:output> </wsdl:operation> </wsdl:binding> − <wsdl:binding name="MessageServiceSoap12Binding" type="ns:MessageServicePortType"> <soap12:binding transport="http://schemas.xmlsoap.org/soap/http"; style="document"/> − <wsdl:operation name="sendMessages"> <soap12:operation soapAction="urn:sendMessages" style="document"/> − <wsdl:input> <soap12:body use="literal"/> </wsdl:input> </wsdl:operation> − <wsdl:operation name="getMessages"> <soap12:operation soapAction="urn:getMessages" style="document"/> − <wsdl:input> <soap12:body use="literal"/> </wsdl:input> − <wsdl:output> <soap12:body use="literal"/> </wsdl:output> </wsdl:operation> </wsdl:binding> On Wed, Oct 15, 2008 at 9:57 PM, keith chapman <[EMAIL PROTECTED]>wrote: > Hi If you take this WSDL<https://mooshup.com/services/system/version?wsdl>[1] > as an example, it has a SOAP 1.1 (system-version-SOAP11Binding) as well > as a SOAP 1.2 (system-version-SOAP12Binding) Binding. If you further look > into its content you will see that they use different namespaces, For e.g > SOAP 1.1 Binding uses "<soap:binding transport=" > http://schemas.xmlsoap.org/soap/http"; style="document"/>" whereas SOAP 1.2 > Binding uses "<soap12:binding transport=" > http://schemas.xmlsoap.org/soap/http"; style="document"/>" and the soap12 > namespace is xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; > whereas the soap namespace is xmlns:soap=" > http://schemas.xmlsoap.org/wsdl/soap/";. > > As you can see there is a difference between the two. > > Thanks, > Keith. > > [1] https://mooshup.com/services/system/version?wsdl > > On Thu, Oct 16, 2008 at 12:35 AM, Bai Shen <[EMAIL PROTECTED]>wrote: > >> I looked at the wsdl again, and there's literally no difference. As far >> as I can tell, they both reference the same namespace. >> >> >> On Wed, Oct 15, 2008 at 2:00 PM, keith chapman <[EMAIL PROTECTED]>wrote: >> >>> The SOAP 1.1 and SOAP 1.2 Bindings look identical but they have a small >>> difference. They indicate to the client what SOAP version to use. If you >>> generate a client specifying the endpoint it will generate it so that the >>> message generated by the client would match the requirements specified in >>> the corresponding binding. You could differentiate between SOAP 1.1 and 1.2 >>> using the namespace. >>> >>> SOAP 1.2 namespace is http://www.w3.org/2003/05/soap-envelope while SOAP >>> 1.1 namespace is http://schemas.xmlsoap.org/soap/envelope/ >>> >>> Thanks, >>> Keith. >>> >>> On Wed, Oct 15, 2008 at 11:14 PM, Bai Shen <[EMAIL PROTECTED]>wrote: >>> >>>> I created a java class, and then used Axis2 to create a web service from >>>> that. However, in the WSDL, it created three connections. A SOAP 1.1, a >>>> SOAP 1.2, and a SOAP HTTP. The SOAP 1.1 and SOAP 1.2 ones look identical >>>> to >>>> me. So I was wondering what the difference was. And is there a need for >>>> them? How does Axis2 know whether it's a 1.1 or 1.2? TIA. >>>> >>>> Bai Shen >>>> >>> >>> >>> >>> -- >>> Keith Chapman >>> Senior Software Engineer >>> WSO2 Inc. >>> Oxygenating the Web Service Platform. >>> http://wso2.org/ >>> >>> blog: http://www.keith-chapman.org >>> >> >> > > > -- > Keith Chapman > Senior Software Engineer > WSO2 Inc. > Oxygenating the Web Service Platform. > http://wso2.org/ > > blog: http://www.keith-chapman.org >
