Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of christian.mueller@gmail.com
 designates 209.85.216.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1332862746098-5598178.post@n5.nabble.com>
References: <1332858352956-5598002.post@n5.nabble.com>
	<CABctVUhDnJH3LfzQc7o8fZWYYjON1CTu16++P-8zhMLDAqXBPQ@mail.gmail.com>
	<1332862746098-5598178.post@n5.nabble.com>
Date: Wed, 28 Mar 2012 08:09:01 +0200
Message-ID: 
 <CALvzYd_QW9ZmKD_1Tu+RiJVvTKXYzvgF4r8mfZMBaggzLC7QWg@mail.gmail.com>
Subject: Re: Have available data in several points of the route?
From: =?ISO-8859-1?Q?Christian_M=FCller?= <christian.mueller@gmail.com>
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=20cf300faf61a64f7c04bc477141

--20cf300faf61a64f7c04bc477141
Content-Type: text/plain; charset=ISO-8859-1

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.blazquez@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.
>

--20cf300faf61a64f7c04bc477141--