>
> The use of "http://www.w3.org/2003/05/soap/bindings/HTTP/" as the
> SOAP 1.2 transport URI does not please some counter-parts using
> alternate implementations:
>
JAXWS generates this as transport binding as when it was implemented in
JAXWS 2.0 FCS there was no SOAP 1.2 binding for WSDL 1.1 and we choce
this URI defined by SOAP 1.2 specification and JAXWS 2.0 spec.
> "This URI identifies the SOAP/HTTP binding within SOAP, not within
> WSDL. Within WSDL the right transport identifier is the one expressed
> in the WSDL11SOAP12 binding document:
> http://www.w3.org/Submission/wsdl11soap12/"
>
> ... which is just a submission at this point.
> What's our position here?
>
This problem is more complicated as there are vendors that support the
soap 1.2 transport URI (like jaxws) too and that includes .NET. Not
sure if its going recommendation anytime soon. IMO, we dont want to
publish a WSDL with something that is not final and possibly URI may
change in recommendation. What should really happen is that the runtime
accepts such transport bindings.
> Since this is just a logical URI, when building a web service
> from WSDL with "http://www.w3.org/2003/05/soap/bindings/HTTP/",
> could the published WSDL have a different URI to make the
> accommodate other WS tools (while preserving interop of course)?
>
I dont see how we can do it without user intervention - such as you
package the wsdl by yourself and modify the transport binding. Its ugly
but there is no 109 descriptor or annotation that would allow users to
pass such uri for the transport binding.
-vivek
> thanks,
> -Alexis
>