You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Tomislav Mrkus (JIRA)" <ji...@apache.org> on 2011/09/21 14:09:08 UTC

[jira] [Updated] (CAMEL-4472) HazelcastComponentHelper. copyHeaders() creates an Out message

     [ https://issues.apache.org/jira/browse/CAMEL-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomislav Mrkus updated CAMEL-4472:
----------------------------------

    Attachment: CAMEL-4472.patch

> HazelcastComponentHelper. copyHeaders() creates an Out message
> --------------------------------------------------------------
>
>                 Key: CAMEL-4472
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4472
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-hazelcast
>            Reporter: Tomislav Mrkus
>         Attachments: CAMEL-4472.patch
>
>
> Due to lazy creation of Out message in DefaultExchange.getOut() implementation, HazelcastComponentHelper.copyHeaders() method inadvertently creates an Out message if one has not been set yet, which then creates problems in CamelInvocationHandler.getBody() which then returns null as a result. 
> There should be a check in copyHeaders() to see if Out exists, e.g.: 
> {code}
> // set out headers 
> if (ex.hasOut()) { 
>     ex.getOut().setHeaders(headers); 
> } 
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira