Thanks Christian. I was wondering, what about if I need a context to store objects and access them from a different exchange (next on one the same route)? But probably in this case the best option is to have context object in the Registry and access registry from each exchange. hhhmm
Bilgin On 28 March 2012 07:09, Christian Müller <christian.muel...@gmail.com>wrote: > Yes, but > - you can store your data as Exchange properties > - you can use the enrich pattern [1] to enrich your message or message > headers and use an AggregationStrategy to merge the old and the new > Exchange together. > > claim-check is the prefered solution if you deal with big data. > > [1] http://camel.apache.org/content-enricher.html > [2] http://camel.apache.org/aggregator2.html > > Best, > Christian > > On Tue, Mar 27, 2012 at 5:39 PM, m.jimen.blazquez < > m.jimen.blazq...@gmail.com> wrote: > > > Hi, > > > > Actually the exchange does not fit because I have to interact with > > services > > which doesn't understand CAMEL so the body in exchange will always be the > > returned object of the invoked method, won't it? > > > > best regards > > > > -- > > View this message in context: > > > http://camel.465427.n5.nabble.com/Have-available-data-in-several-points-of-the-route-tp5598002p5598178.html > > Sent from the Camel - Users mailing list archive at Nabble.com. > > >
