Hi You can always store values as properties on the exchange which will be available there for the lifecycle of the exchange.
Then you can later get access to that property and store it somewhere in the message body or as a header of the message, or what you want. On Sun, Jan 5, 2014 at 3:21 AM, camel user <cameluser2...@yahoo.in> wrote: > Greetings! I have a problem holding a value in camel blueprint. Please help > me resolve it > > > For e.g., I have 2 to 3 routes, > In my first route, I will hit a service URI and save the response xml from > the service in a property,say 'outputXML'. > > I want the outputXML to be available in all the other routes irrespective of > whether I hit another service URI or use XSLT in the succeeding routes. > > Thanks! -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen Make your Camel applications look hawt, try: http://hawt.io
