Perhaps this helps: http://stackoverflow.com/questions/10330998/passing-values-between-processors-in-apache-camel . Check Claus answer.
On Tue, Jun 3, 2014 at 1:17 PM, Minh Tran <darth.minhs...@gmail.com> wrote: > Hi > > That's because the camel property doesn't actually get put onto a JMS > message property. I know this sounds confusing but the camel property does > not match JMS message properties. Try and put it on a camel header instead, > > The reason why a direct call to route 3 works is because it's run under > the same route execution so the property gets propagated across but it > doesn't survive the JMS trip because camel properties don't get propagated > there. Hope that makes sense. > > On 02/06/2014, at 11:41 PM, Happy User <happyuser828...@gmail.com> wrote: > > > I wonder if anyone could help me with this. > > > > 1. Setting Xpath value in a property in route 1 > > 2. Setting a body and placing in Topic in route 1 > > 3. Reading the value from Topic in route 2 > > 4. Am trying to print the property set in Step 1 but am getting null > > 5. Calling another route 3 from route 2 > > 6. Printing the property set in Step 1 but again null. > > > > If I call the route 3 from route 1 instead of route 2, am getting the > value > > when I print the property. But I want to call route 3 only after route 2 > > completes as I want to process the value from Topic in route 3. > > > > What is missing here? > >
