Hi Garry, No worries, if you are looking to do something each time a message is sent to the ActiveMQ Endpoint you could just stick a processor in.
Thanks Graham <camel:route id="routeLegacyDestinationEntry" routePolicyRef="loggingRoutePolicy"> <camel:from ref="legacyDestinationEntry" /> <camel:to uri="bean://legacyDestinationConsumer?method=process" /> <camel:split parallelProcessing="true" streaming="true"> <camel:simple>${body.envelopeList}</camel:simple> <camel:to ref="localSmsDeliveryEntry" /> <camel:process ref="myMessageProcess" /> </camel:split> </camel:route> > Date: Wed, 29 Aug 2012 14:41:10 -0700 > From: garryd...@gmail.com > To: users@camel.apache.org > Subject: RE: RoutePolicy + Split > > Hi Graham > > Thanx a lot for your replies. > > I´ll try another approach to do what I want. > > The localSmsDeliveryEntry is an activemq endpoint. I thought that splited > Exchanges could fire onExchangeDone because they heir its parent Exchange > headers, including correlationID, and localSmsDeliveryEntry is the last > endpoint in my route. > > Thanks again > > []s > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/RoutePolicy-Split-tp5718325p5718335.html > Sent from the Camel - Users mailing list archive at Nabble.com.