CamelTemplate.extractResultBody question

[William Tam <em...@gmail.com>]

In org.apache.camel.CamelTemplate, shouldn't it just return null if
result.getOut().getBody() is null?  Why does it return the IN body as
a result?


   protected Object extractResultBody(E result) {
        Object answer = null;
        if (result != null) {
            answer = result.getOut().getBody();
            if (answer == null) {
                answer = result.getIn().getBody();
            }
        }

Regards,
William

Re: CamelTemplate.extractResultBody question

[James Strachan <ja...@gmail.com>]

On 03/10/2007, William Tam <em...@gmail.com> wrote:
> In org.apache.camel.CamelTemplate, shouldn't it just return null if
> result.getOut().getBody() is null?  Why does it return the IN body as
> a result?
>
>
>    protected Object extractResultBody(E result) {
>         Object answer = null;
>         if (result != null) {
>             answer = result.getOut().getBody();
>             if (answer == null) {
>                 answer = result.getIn().getBody();
>             }
>         }

Now we have the message exchange pattern stuff integrated it might;
previously a Processor could have mutated an IN message; or could have
generated an OUT message and so it was hard to work with both kinds of
processors nicely.

-- 
James
-------
http://macstrac.blogspot.com/

Open Source SOA
http://open.iona.com