http-component endpoint targets

[Ilya Kuleshov <ik...@naumen.ru>]

Hello everyone!

Manual says that although service and endpoint attributes are required
by the consumer endpoint definition of http-component, it is possible
to use WS-Addressing to set custom target for the SOAP message. When I
use the WSA:To header then value from this header overrides default
service/endpoint correctly.

On the other side, when I use the WSA:Action header then
http-component sets destination interface/operation attributes of the
message as expected but leaves service/endpoint attributes from the
http endpoint definition. This results into routing problems because
the JBI message now has interface, operation, service and endpoint
attributes set altogether.

IMHO this is not the desired behaviour and only interface/operation
should be set in case of the WSA:Action header.

I ran into this issue by trying the BPE component. I can't use static
targetService and targetEndpoint endpoint properties because dynamic
routing based on the WSA headers is required.

Cheers!

Re: Re[2]: http-component endpoint targets

[cory <co...@gmail.com>]

There is some command and control functionality.  Check out
org.apache.ode.bpe.cc.base.CCServiceBase.  Maybe some of this could be
exposed through the extension mbean?

-cory

On 4/12/06, Ilya Kuleshov <ik...@naumen.ru> wrote:
> Hi, Guillaume!
>
> GN> I guess you have hit an issue.
> GN> Could you please raise a JIRA for that ?
>
> Done. Thanks for a rapid reply.
>
> I also want to ask whether it is a right place for the Ode(BPE) engine
> questions? If so then is there any management interface that allows to
> get the list of active processes and other stat info? I have not found
> any.
>
> I decided to switch to the Ode at least for a short time before there
> will be some working JBI binding for PXE. It is really boring to
> discover new bugs and recompile PXE JBI component each time the
> Servicemix code changes. Ode seems to work great, does not require
> additional descriptor like pxe-system.xml and allows jbi bindings to
> be defined right in the WSDL document. But it appears that Ode has
> no any configuration and management tools available.
>
> GN> On 4/12/06, Ilya Kuleshov <ik...@naumen.ru> wrote:
> >> Hello everyone!
> >>
> >> Manual says that although service and endpoint attributes are required
> >> by the consumer endpoint definition of http-component, it is possible
> >> to use WS-Addressing to set custom target for the SOAP message. When I
> >> use the WSA:To header then value from this header overrides default
> >> service/endpoint correctly.
> >>
> >> On the other side, when I use the WSA:Action header then
> >> http-component sets destination interface/operation attributes of the
> >> message as expected but leaves service/endpoint attributes from the
> >> http endpoint definition. This results into routing problems because
> >> the JBI message now has interface, operation, service and endpoint
> >> attributes set altogether.
> >>
> >> IMHO this is not the desired behaviour and only interface/operation
> >> should be set in case of the WSA:Action header.
> >>
> >> I ran into this issue by trying the BPE component. I can't use static
> >> targetService and targetEndpoint endpoint properties because dynamic
> >> routing based on the WSA headers is required.
> >>
> >> Cheers!
> >>
> >>
>
>
>
>

Re[2]: http-component endpoint targets

[Ilya Kuleshov <ik...@naumen.ru>]

Hi, Guillaume!

GN> I guess you have hit an issue.
GN> Could you please raise a JIRA for that ?

Done. Thanks for a rapid reply.

I also want to ask whether it is a right place for the Ode(BPE) engine
questions? If so then is there any management interface that allows to
get the list of active processes and other stat info? I have not found
any.

I decided to switch to the Ode at least for a short time before there
will be some working JBI binding for PXE. It is really boring to
discover new bugs and recompile PXE JBI component each time the
Servicemix code changes. Ode seems to work great, does not require
additional descriptor like pxe-system.xml and allows jbi bindings to
be defined right in the WSDL document. But it appears that Ode has
no any configuration and management tools available.

GN> On 4/12/06, Ilya Kuleshov <ik...@naumen.ru> wrote:
>> Hello everyone!
>>
>> Manual says that although service and endpoint attributes are required
>> by the consumer endpoint definition of http-component, it is possible
>> to use WS-Addressing to set custom target for the SOAP message. When I
>> use the WSA:To header then value from this header overrides default
>> service/endpoint correctly.
>>
>> On the other side, when I use the WSA:Action header then
>> http-component sets destination interface/operation attributes of the
>> message as expected but leaves service/endpoint attributes from the
>> http endpoint definition. This results into routing problems because
>> the JBI message now has interface, operation, service and endpoint
>> attributes set altogether.
>>
>> IMHO this is not the desired behaviour and only interface/operation
>> should be set in case of the WSA:Action header.
>>
>> I ran into this issue by trying the BPE component. I can't use static
>> targetService and targetEndpoint endpoint properties because dynamic
>> routing based on the WSA headers is required.
>>
>> Cheers!
>>
>>

Re: http-component endpoint targets

[Guillaume Nodet <gn...@gmail.com>]

I guess you have hit an issue.
Could you please raise a JIRA for that ?

Cheers,
Guillaume Nodet

On 4/12/06, Ilya Kuleshov <ik...@naumen.ru> wrote:
> Hello everyone!
>
> Manual says that although service and endpoint attributes are required
> by the consumer endpoint definition of http-component, it is possible
> to use WS-Addressing to set custom target for the SOAP message. When I
> use the WSA:To header then value from this header overrides default
> service/endpoint correctly.
>
> On the other side, when I use the WSA:Action header then
> http-component sets destination interface/operation attributes of the
> message as expected but leaves service/endpoint attributes from the
> http endpoint definition. This results into routing problems because
> the JBI message now has interface, operation, service and endpoint
> attributes set altogether.
>
> IMHO this is not the desired behaviour and only interface/operation
> should be set in case of the WSA:Action header.
>
> I ran into this issue by trying the BPE component. I can't use static
> targetService and targetEndpoint endpoint properties because dynamic
> routing based on the WSA headers is required.
>
> Cheers!
>
>