camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <>
Subject Re: Stream Caching 101
Date Thu, 21 Mar 2013 21:59:03 GMT
We documented this feature here:


On Thu, Mar 21, 2013 at 5:23 PM, rouble <> wrote:

> Camel-o-philes,
> Can someone give me a quick understanding of what it means if I enable
> stream caching? Does it mean that in a single processor I can read the
> IN or OUT message as many times as I like? It does not seem to be this
> way. I can easily recreate a situation if I try to read a message the
> second time in the same processor, I get an empty string (not null,
> empty). Am I missing something?
> For my use case, of pretty printing the body when it enters a
> processor, and when it leaves the same processor I need to be able to
> read the message multiple times in the same processor. For this I am
> having to re-set it back after every read - which sort of kills the
> purpose of enabling stream caching - but maybe this is not how it was
> intended to be used?
> tia,
> rouble


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message