Right, or you may be able to use the EIP recipient list pattern to forward a copy of the exchange to multiple JBI endpoints.
On Wed, Jul 23, 2008 at 12:30 PM, Manuel EVENO <[EMAIL PROTECTED]> wrote: > If you need multiple consumer of a message, you should use JMS Topic instead > of JMS Queue. > See http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JMS3.html#wp78715 > > On Wed, Jul 23, 2008 at 12:00 PM, navigator09 <[EMAIL PROTECTED]> > wrote: > >> >> Hi, >> >> I am implementing routing slip pattern in the application. In the pattern >> I have routed the output of the webservice to a jms queue exposed as a >> service using the jms-su. A camel router is listing to the queue and >> processing the response and at the same time I also have a python script >> listiing to messages from the same queue. >> >> I requirement is the messages on the queue needs to be processed further >> by the camel router and at the same time should be available for the python >> script for display. But the messages routed by the routing slip to the >> queue >> are available to the camel router only. They are not even registered on the >> jconsole queue status. >> >> Are messages sent internally thorough su not available to the external >> listeners? >> >> >> >> The configuration of routing slip >> >> <eip:static-routing-slip service="replaceMe:routingSlip" >> endpoint="endpoint"> >> <eip:targets> >> <eip:exchange-target service="scmservice:SCMService" /> >> <eip:exchange-target service="tutorial:jms" endpoint="provider"/> >> </eip:targets> >> </eip:static-routing-slip> >> >> >> >> Regards, >> Ganesh >> >> -- >> View this message in context: >> http://www.nabble.com/understanding-the-working-of-routing-slip-in-servicemix-eip-tp18607456p18607456.html >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
