Jitendra Kotamraju wrote:
> Kohsuke Kawaguchi wrote:
>
>> Oleksiy Stashok wrote:
>>
>>> Hi,
>>>
>>> is there any way how to specify binding transport to non http one?
>>> Let's say:
>>> <soap:binding transport="http://schemas.xmlsoap.org/soap/tcp"
>>> style="document" />
>>> or any else.
>>>
>>> As when i try to put something else - then wsimport says
>>> "unrecognized transport", but actual jax-ws code seems ignoring that
>>> at all, just checking binding element namespace.
>>
>>
>> Paul is right. The runtime has all the code that supports pluggable
>> transports, but I believe no work has done for the tool.
>>
>> Perhaps you can send the complete WSDL or something so that someone
>> from the JAX-WS team can look into it?
>>
> also ccing jax-ws alias. At present, WSDLModeler.java is not accepting
> anyother transports. Something needs to be looked at.
>
> 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;
> }
>
wsimport fails inorder to be compoiant with the spec. Probably this code
should be changed so that non-http transports are allowed with
-extension switch on wsimport.
-vivek.
> Jitu
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jax-ws.dev.java.net
> For additional commands, e-mail: dev-help_at_jax-ws.dev.java.net
>