You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by brwccobb <cr...@broadwing.com> on 2006/11/01 19:47:45 UTC
Subscription not going to ExchangeListener
I have an ExchangeListener configured on the container that is getting called
as messages flow fromone component to the next through target service calls.
However, I have other components that get messages through a
SubscriptionSpec, and the those MessageExchanges never hit my
ExchangeListener.
Is there anyway to have components called throug a SubscriptionSpec go to
the ExchangeListener?
--
View this message in context: http://www.nabble.com/Subscription-not-going-to-ExchangeListener-tf2555082.html#a7119914
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Subscription not going to ExchangeListener
Posted by brwccobb <cr...@broadwing.com>.
Thanks. That helped my find a bug in my ExchangeListner that aborted if the
exchange service is null. I needed to dig deeper to find the data I need in
the listener.
gnodet wrote:
>
> Exchanges using SubscriptionSpec do not go directly
> from the sender component to the subscriber, as one
> exchange may only be sent to one target. Thus,
> an intermediary component named #SubscriptionManager#
> is given the exchange and send a copy to all subscribers.
> As it used the standard way to send messages, there is
> no reason why you could not intercept it, however the
> source component will not be the sender, but the subscription
> manager.
>
> On 11/1/06, brwccobb <cr...@broadwing.com> wrote:
>>
>> I have an ExchangeListener configured on the container that is getting
>> called
>> as messages flow fromone component to the next through target service
>> calls.
>>
>> However, I have other components that get messages through a
>> SubscriptionSpec, and the those MessageExchanges never hit my
>> ExchangeListener.
>>
>> Is there anyway to have components called throug a SubscriptionSpec go to
>> the ExchangeListener?
>> --
>> View this message in context:
>> http://www.nabble.com/Subscription-not-going-to-ExchangeListener-tf2555082.html#a7119914
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
>
>
--
View this message in context: http://www.nabble.com/Subscription-not-going-to-ExchangeListener-tf2555082.html#a7121797
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Subscription not going to ExchangeListener
Posted by Guillaume Nodet <gn...@gmail.com>.
Exchanges using SubscriptionSpec do not go directly
from the sender component to the subscriber, as one
exchange may only be sent to one target. Thus,
an intermediary component named #SubscriptionManager#
is given the exchange and send a copy to all subscribers.
As it used the standard way to send messages, there is
no reason why you could not intercept it, however the
source component will not be the sender, but the subscription
manager.
On 11/1/06, brwccobb <cr...@broadwing.com> wrote:
>
> I have an ExchangeListener configured on the container that is getting called
> as messages flow fromone component to the next through target service calls.
>
> However, I have other components that get messages through a
> SubscriptionSpec, and the those MessageExchanges never hit my
> ExchangeListener.
>
> Is there anyway to have components called throug a SubscriptionSpec go to
> the ExchangeListener?
> --
> View this message in context: http://www.nabble.com/Subscription-not-going-to-ExchangeListener-tf2555082.html#a7119914
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet