Hi,
I have a unique problem with a value created in one of the sub-routes in a
multicast to be used in another.
Eg:
<multicast stopOnException="true">
<to uri="direct:archive"/>
<to uri="direct:validate"/>
<to uri="direct:process1"/>
<to uri="direct:process2"/>
<to uri="direct:end_process"/>
</multicast>
the route process1 runs some business rules and generates parameters that
needs to be accessed by end_process.
I tried both setHeader and setProperty, but they don't seem to be available
beyond the scope of process1.
I was assuming that setProperty would set the property on the Exchange and
so should be accessible throughout the lifecycle of the Exchange..
Thanks
Rakesh
--
View this message in context:
http://camel.465427.n5.nabble.com/exchange-property-scope-tp5749945.html
Sent from the Camel - Users mailing list archive at Nabble.com.