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;
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
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
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
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
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
