Regarding multiple <to..> recipients

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Regarding multiple <to..> recipients

sinavolu
This is with respect to the mailing list
http://www.nabble.com/multiple-%3Cto--%3E-recipients-td19742033s22882.ht
ml#a19742033 and the related JIRA
https://issues.apache.org/activemq/browse/CAMEL-958

 

This information in the mailing list is not in accordance to the
documentation of

http://activemq.apache.org/camel/recipient-list.html (JIRA CAMEL 958
logged for this).

 

But public subscribe pattern and wire-tap pattern also has the same
issue.

http://activemq.apache.org/camel/publish-subscribe-channel.html

http://activemq.apache.org/camel/wire-tap.html

 

For example,

 

<camelContext id="camel"
xmlns="http://activemq.apache.org/camel/schema/spring">
  <route>
    <from uri="seda:a"/>
    <to uri="seda:tap"/>
    <to uri="seda:b"/>
  </route>
</camelContext>

 

This won't be a wire tap, because output of seda:tap will go to seda:b.
According to EIP
http://www.enterpriseintegrationpatterns.com/WireTap.html, a wire tap
should send the same message to both the channels seda:tap and seda:b
(similar to a recipient list).

 

The same thing with publish subscribe patterns.

 

Thanks

Suresh

 

Reply | Threaded
Open this post in threaded view
|

Re: Regarding multiple <to..> recipients

Domingo Suárez Torres
You  can use multicast:http://activemq.apache.org/camel/multicast.html


Cheers

2008/10/3 Suresh Inavolu <[hidden email]>

> This is with respect to the mailing list
> http://www.nabble.com/multiple-%3Cto--%3E-recipients-td19742033s22882.ht
> ml#a19742033<http://www.nabble.com/multiple-%3Cto--%3E-recipients-td19742033s22882.html#a19742033>and the related JIRA
> https://issues.apache.org/activemq/browse/CAMEL-958
>
>
>
> This information in the mailing list is not in accordance to the
> documentation of
>
> http://activemq.apache.org/camel/recipient-list.html (JIRA CAMEL 958
> logged for this).
>
>
>
> But public subscribe pattern and wire-tap pattern also has the same
> issue.
>
> http://activemq.apache.org/camel/publish-subscribe-channel.html
>
> http://activemq.apache.org/camel/wire-tap.html
>
>
>
> For example,
>
>
>
> <camelContext id="camel"
> xmlns="http://activemq.apache.org/camel/schema/spring">
>  <route>
>    <from uri="seda:a"/>
>    <to uri="seda:tap"/>
>    <to uri="seda:b"/>
>  </route>
> </camelContext>
>
>
>
> This won't be a wire tap, because output of seda:tap will go to seda:b.
> According to EIP
> http://www.enterpriseintegrationpatterns.com/WireTap.html, a wire tap
> should send the same message to both the channels seda:tap and seda:b
> (similar to a recipient list).
>
>
>
> The same thing with publish subscribe patterns.
>
>
>
> Thanks
>
> Suresh
>
>
>
>


--
domix
Reply | Threaded
Open this post in threaded view
|

RE: Regarding multiple <to..> recipients

Claus Ibsen
Hi

Cheers. I have fixed the wiretap samples to use multicast.


Med venlig hilsen
 
Claus Ibsen
......................................
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
Web: www.silverbullet.dk

-----Original Message-----
From: Domingo Suárez Torres [mailto:[hidden email]]
Sent: 3. oktober 2008 17:50
To: [hidden email]
Subject: Re: Regarding multiple <to..> recipients

You  can use multicast:http://activemq.apache.org/camel/multicast.html


Cheers

2008/10/3 Suresh Inavolu <[hidden email]>

> This is with respect to the mailing list
> http://www.nabble.com/multiple-%3Cto--%3E-recipients-td19742033s22882.ht
> ml#a19742033<http://www.nabble.com/multiple-%3Cto--%3E-recipients-td19742033s22882.html#a19742033>and the related JIRA
> https://issues.apache.org/activemq/browse/CAMEL-958
>
>
>
> This information in the mailing list is not in accordance to the
> documentation of
>
> http://activemq.apache.org/camel/recipient-list.html (JIRA CAMEL 958
> logged for this).
>
>
>
> But public subscribe pattern and wire-tap pattern also has the same
> issue.
>
> http://activemq.apache.org/camel/publish-subscribe-channel.html
>
> http://activemq.apache.org/camel/wire-tap.html
>
>
>
> For example,
>
>
>
> <camelContext id="camel"
> xmlns="http://activemq.apache.org/camel/schema/spring">
>  <route>
>    <from uri="seda:a"/>
>    <to uri="seda:tap"/>
>    <to uri="seda:b"/>
>  </route>
> </camelContext>
>
>
>
> This won't be a wire tap, because output of seda:tap will go to seda:b.
> According to EIP
> http://www.enterpriseintegrationpatterns.com/WireTap.html, a wire tap
> should send the same message to both the channels seda:tap and seda:b
> (similar to a recipient list).
>
>
>
> The same thing with publish subscribe patterns.
>
>
>
> Thanks
>
> Suresh
>
>
>
>


--
domix