Hi,
The message body does not be changed, it's just because of you need to
call the cache's rest in the processor.
I just added simple unit test[1] to show how to avoid that issue.
When you print out the message body, the input stream has been read, if
you don't call the cache's rest method, jet
this message in context:
http://www.nabble.com/Body-lost-with-Jetty-component-tp24091800p24093758.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Yes, no it works.
I have downloaded Camel 2.0-M2 Release and i get the correct console output!
Thanks for your quick answer.
--
View this message in context:
http://www.nabble.com/Body-lost-with-Jetty-component-tp24091800p24093508.html
Sent from the Camel - Users mailing list archive at
Im using binary distribution version 2.0-M1
--
View this message in context:
http://www.nabble.com/Body-lost-with-Jetty-component-tp24091800p24093362.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
Which version of Camel are you using?
It looks like you are using a old camel version which doesn't enable the
stream caching , so you can't read the input stream more than twice.
Willem
SwenVogel wrote:
> Hi,
>
> im playing around with the jetty component and encountered the problem that
>
nsole output is:
Process body = HelloWorld
Process body =
but why it is not:
Process body = HelloWorld
Process body = HelloWorld
--
View this message in context:
http://www.nabble.com/Body-lost-with-Jetty-component-tp24091800p24091800.html
Sent from the Camel - Users mailing list archive at Nabble.com.