It could be that you need to strip replyTo headers, a message-properties-transformer can help.
Andrew
On Jun 9, 2009 9:57 AM, "n4d4br0v1tchk4" <n4d4br0v1tchk4@...> wrote:
Hi all,
I'm trying to set up a configuration for mule that does not appear to be
trivial. I've gone through all the messaging style descriptions and
tutorials and still haven't figured it out. Basically what I want is to get
some "service encapsulation" that I'm not getting.
I want to call a number of services using multicast routing and then to have
each of them call a number of other services in a chaining-router and then
that the resulting message of those chains are returned asynchronously to
the reply-to address. But regardless of what I do, the service that is
called by the multicasting-router always returns the asynch message when the
*first* service in the chain returns, and not when the last one returns...
How can I call a series of services in chain so that the asynch message
comes from the last service in the chain?
Thanks!
João
--
View this message in context: http://www.nabble.com/Configuring-service-encapsulation-tp23947021p23947021.html
Sent from the Mule - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
