camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Kalukiewicz" <roman.kalukiew...@gmail.com>
Subject Re: Explanation of MEPs within Camel
Date Fri, 18 Apr 2008 11:01:54 GMT
2008/4/18, James Strachan <james.strachan@gmail.com>:
> On 17/04/2008, David Siefert <siefert.david.mailinglist@gmail.com> wrote:
>  > Some updates from more investigation:
>  >
>  >  1. If I do not set the body in the output message, I get my input message
>  >  back (regardless of the header properties that were set).
>
>
> Ah - I think that currently the code assumes if no body is set then
>  the OUT is empty, so reuse the IN. I wonder if we should fix that?

In fact currently we reuse IN if there is no OUT message at all - not
when OUT [body] is empty. This way if you set a header and leave the
body empty, then this header will be propagated. If you only call
getOut() it will lazy create an empty OUT message, and it will be
propagated.

Roman

Mime
View raw message