There is already issue filed,
https://jax-ws.dev.java.net/issues/show_bug.cgi?id=34. This will be
fixed for jaxws 2.1 ri release.
-vivek.
Oleksiy Stashok wrote:
> Hi,
>
> im trying to find a way how wsimport can generate artifacts when WSDL
> file has non-standard transport binding (not HTTP).
> Several times i've heard something about -extension could be used, but
> not really sure how.
> Looking at /WSDLModeler/ (for sure if its right place to look ;) ) -
> its definitly unclear how custom transport could be processed.
> Regarding this
> /
> if (soapBinding.getTransport() == null
> || (!soapBinding.getTransport().equals(
> SOAPConstants.URI_SOAP_TRANSPORT_HTTP) &&
> !soapBinding.getTransport().equals(
> SOAP12Constants.URI_SOAP_TRANSPORT_HTTP))) {
> // cannot deal with non-HTTP ports
> warn(
>
> "wsdlmodeler.warning.ignoringSOAPBinding.nonHTTPTransport",
> wsdlPort.getName());
> return false;
> }/
>
> So, is there a way to process such custom transport bindings?
>
> Thanks.
>
> WBR,
> Alexey.