Hi, The best way to do this at the moment is by introducing a choice processor before directing the payload to the endpoint(s) and logging the choice when a selection is made using a log component before it is sent to the endpoint. Obviously, there needs to be some way for the choice processor to determine where the payload will be directed.
Hope this helps. Cheers, Ashwin... BAltmiks wrote: > > Hello, > > we would like to persist information (the URIs) of the Route the message > was sent to. > > My Route Definition: > > <camel:camelContext id="camel"> > <camel:route> > <camel:from uri="jms:jms/MessageDispatcherQueue" /> > <camel:transacted ref="PROPAGATION_REQUIRED" /> > <camel:to uri="mqseries:tbextsys.mqseries.yereports"/> > <camel:to uri="mqseries:tbflow.mqseries.yereports"/> > > <camel:transform> > <camel:method bean="TMDMESSAGEConverter" method="doTransform" /> > > </camel:transform> > <camel:to uri="jpa:entity.TMDMessage"/> > </camel:route> > </camel:camelContext> > > The Message is read from a Queue (jms/MessageDispatcherQueue) and is sent > to different Queues (tbextsys.mqseries.yereports and > tbflow.mqseries.yereports). After that we persist the Message-Body. The > Message-Body contains XML-Data. We also would like to persist the > Endpoint-URIs the Message was sent to. In these case the information, that > the Message was sent to tbextsys.mqseries.yereports and > tbflow.mqseries.yereports. Is there a way to do that? > > My Route-Definition in my example is static. In future we want to do it > more dynamically. > > Thanks for your help! > > Regards, > Bernd > > > ----- --- Ashwin Karpe, Principal Consultant, PS - Opensource Center of Competence Progress Software Corporation 14 Oak Park Drive Bedford, MA 01730 --- +1-972-304-9084 (Office) +1-972-971-1700 (Mobile) ---- Blog: http://opensourceknowledge.blogspot.com/ -- View this message in context: http://www.nabble.com/Persist-information-%28the-URIs%29-of-the-Route-the-message-was-sent-to-tp25531018p25531151.html Sent from the Camel - Users mailing list archive at Nabble.com.
