You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@camel.apache.org by Frederic Pirson <fr...@gmail.com> on 2016/03/17 20:19:27 UTC

[Cxf]Problem with the conduit selector

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 http conduit.
When the same cxf:endpoint contains the wsdl location, it tries to use the
JMS conduit !

I don't know if it s the expected behavior, but I think the conduit should
be selected by the given address instead of the transport inside the wsdl ;
or the conduit to use should be specified in the cxf:endpoint ?



Regards

Frédéric Pirson

Re: [Cxf]Problem with the conduit selector

Posted by Frederic Pirson <fr...@gmail.com>.

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 <fr...@gmail.com>:

> 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 the conduit based on
> the wsdl services when the protocol of the address of the cxf endpoint says
> something other.
>
> Regards
>
> Frédéric
>
> 2016-03-18 9:16 GMT+01:00 Morgan Hautman <mo...@gmail.com>:
>
>> 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 <fr...@gmail.com>:
>>
>> > 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 http conduit.
>> > When the same cxf:endpoint contains the wsdl location, it tries to use
>> the
>> > JMS conduit !
>> >
>> > I don't know if it s the expected behavior, but I think the conduit
>> should
>> > be selected by the given address instead of the transport inside the
>> wsdl ;
>> > or the conduit to use should be specified in the cxf:endpoint ?
>> >
>> >
>> >
>> > Regards
>> >
>> > Frédéric Pirson
>> >
>>
>
>

Re: [Cxf]Problem with the conduit selector

Posted by Frederic Pirson <fr...@gmail.com>.

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 the conduit based on
the wsdl services when the protocol of the address of the cxf endpoint says
something other.

Regards

Frédéric

2016-03-18 9:16 GMT+01:00 Morgan Hautman <mo...@gmail.com>:

> 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 <fr...@gmail.com>:
>
> > 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 http conduit.
> > When the same cxf:endpoint contains the wsdl location, it tries to use
> the
> > JMS conduit !
> >
> > I don't know if it s the expected behavior, but I think the conduit
> should
> > be selected by the given address instead of the transport inside the
> wsdl ;
> > or the conduit to use should be specified in the cxf:endpoint ?
> >
> >
> >
> > Regards
> >
> > Frédéric Pirson
> >
>

Re: [Cxf]Problem with the conduit selector

Posted by Morgan Hautman <mo...@gmail.com>.

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 <fr...@gmail.com>:

> 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 http conduit.
> When the same cxf:endpoint contains the wsdl location, it tries to use the
> JMS conduit !
>
> I don't know if it s the expected behavior, but I think the conduit should
> be selected by the given address instead of the transport inside the wsdl ;
> or the conduit to use should be specified in the cxf:endpoint ?
>
>
>
> Regards
>
> Frédéric Pirson
>