There was earlier discussion and issue[1]on jaxws about generating wsdl
binding and port for SOAP/TCP. As I understand that the generated WSDL
will have wsdl:binding/soapbind:binding_at_transport with an implementation
specific TCP transport URI. This will tell the runtime whether the
transport is TCP vs HTTP.
Considering this fact
1. We don't need to generate WS-Policy assertion for tcp transport
2. Can we use BindingType() annotation on the endpoint class or SEI for
SOAP/HTTP and TCP transport?
- For example the URI for BindingType could be something like:
http://schemas.xmlsoap.org/wsdl/soap/http?tcp - soap 11/http and
soap11/tcp bindings
http://www.w3.org/2003/05/soap/bindings/HTTP/ - soap12/http and
soap12/tcp bindings
some-uri-for-soap-tcp - Only soap/tcp binding
- This will not require uses of wsit config file to indicate TCP
feature is enabled and the generated WSDL should have TCP transport binding
- This will make it easy generating TCP transport binding for each
SOAP/HTTP port in the generated WSDL.
With this approach, JAXWS can simply determine that it needs to generate
SOAP/TCP binding. Comments?
-vivek.
[1]
https://jax-ws.dev.java.net/issues/show_bug.cgi?id=40