And you can always use a processor to copy stuff from the original exchange and set them as property on the exchange. Then you can fetch this information again with getProperty.
Properties should be preserved during routing - well unless you route it over JMS / Mina etc. On Tue, Apr 14, 2009 at 7:04 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > On Tue, Apr 14, 2009 at 6:59 AM, huntc <hu...@mac.com> wrote: >> >> Thanks Claus - looks as though I'll have to wait for v2.0. > In Camel 1.x the multicast and aggregator have a similar feature, eg > AggregationStrategy. > > So you could do it with one of them instead of the enrich DSL. > > >> -- >> View this message in context: >> http://www.nabble.com/Storing-context-with-exchanges-tp23017939p23033262.html >> Sent from the Camel - Users (activemq) mailing list archive at Nabble.com. >> >> > > > > -- > Claus Ibsen > Apache Camel Committer > > Open Source Integration: http://fusesource.com > Blog: http://davsclaus.blogspot.com/ > Twitter: http://twitter.com/davsclaus > Apache Camel Reference Card: > http://refcardz.dzone.com/refcardz/enterprise-integration > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus Apache Camel Reference Card: http://refcardz.dzone.com/refcardz/enterprise-integration
