One caveat is that if y, for instance, is an InOnly than z will not
receive the out of y (null), but the *in* of y.
Cheers
Hadrian
On Mar 28, 2008, at 4:17 AM, James Strachan wrote:
On 27/03/2008, raulvk <[EMAIL PROTECTED]> wrote:
Aaron,
Thanks a lot for your help. I will follow your tip and will notch the
logging level up to DEBUG ;)
However, as far as I know (I've read this somewhere but I can't
recall
where), when you specify multiple recipients following the syntax you
specified (multiple <to> elements or <multicast>), what happens is
that the
same initial message gets routed to all the recipients.
What I want to
achieve is a "sequence of invocations", where each recipient gets
the result
of the processing done by the previous one.
Yes thats what happens when you use the first form...
<route>
<from uri="direct:a"/>
<to uri="direct:x"/>
<to uri="direct:y"/>
<to uri="direct:z"/>
<to uri="mock:result"/>
</route>
that is the result of x is sent to y and the result of that sent to
z etc.
If you want the same message to be sent separately to each endpoint,
then thats what <multicast> does (i.e. each recipient gets its own
copy).
<route>
<from uri="direct:a"/>
<multicast>
<to uri="direct:x"/>
<to uri="direct:y"/>
<to uri="direct:z"/>
<to uri="mock:result"/>
</multicast>
</route>
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://open.iona.com
