Solution found, it is possible to override the transport by setting the
transportId on the cxf:endpoint.
Thanks
2016-03-18 10:04 GMT+01:00 Frederic Pirson :
> Hi Morgan,
>
> Thanks for reply.
>
> Hi agree with the specs, but since the wsdl is not provided in my first
> case, it selects the condu
Hi Morgan,
Thanks for reply.
Hi agree with the specs, but since the wsdl is not provided in my first
case, it selects the conduit well (based on the address), but when the wsdl
is set in the cxf:endpoint, it doesn"t take account of the address
protocol. According to me it makes no sense to select
Hi Fred,
Per spec it is the intended behavior.
ref: https://www.w3.org/TR/wsdl#_soap:binding
https://www.w3.org/TR/wsdl#_soap:address
Regards,
Morgan
2016-03-17 20:19 GMT+01:00 Frederic Pirson :
> Hello,
>
> I don't know if it is a concern for camel or cxf.
>
>
> For a project, we are using a
Hello,
I don't know if it is a concern for camel or cxf.
For a project, we are using a soap webserivce with contract first.
In the wsdl, the transport is specified as jms (SOAP/jms).
When I make a cxf:endpoint with a http address without the wsdl location in
it, it works perfectly by using the
