> You can always store values as properties on the exchange which will
> be available there for the lifecycle of the exchange.
And if the value need to be accessible between multiple external
interactions with the router, you can temporary store it in a cache
[1] component.
[1] http://camel.apach
, camel user 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 '
Any help?
--
View this message in context:
http://camel.465427.n5.nabble.com/Holding-a-value-in-camel-blueprint-tp5745558p5745688.html
Sent from the Camel - Users mailing list archive at Nabble.com.
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
