Hi Thanks for reporting. Do you mind creating a JIRA ticket for this bug?
There is a link to JIRA from here http://camel.apache.org/support And as we love contributions, you are welcome to work on a patch as well. On Wed, Sep 21, 2011 at 11:48 AM, Tomislav Mrkus <[email protected]> wrote: > Hi, > > 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.: > // set out headers > if (ex.hasOut()) { > ex.getOut().setHeaders(headers); > } > > Tomislav > > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/HazelcastComponentHelper-copyHeaders-issue-tp4825799p4825799.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
