Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.215.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1316598523379-4825799.post@n5.nabble.com>
References: <1316598523379-4825799.post@n5.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Wed, 21 Sep 2011 12:47:28 +0200
Message-ID: 
 <CAGB5yNmu1tRSDH-iP0BhYtMJmEMETPUJad_P9CeS7+yrPgEDtw@mail.gmail.com>
Subject: Re: HazelcastComponentHelper copyHeaders issue
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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 <tmrkus@gmail.com> wrote:
> Hi,
>
> due to lazy creation of Out message in DefaultExchange.getOut()
> implementation, HazelcastComponentHelper.copyHeaders() method inadvertent=
ly
> 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.:
> =A0// set out headers
> =A0if (ex.hasOut()) {
> =A0 =A0 =A0 =A0ex.getOut().setHeaders(headers);
> =A0}
>
> Tomislav
>
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Hazelcast=
ComponentHelper-copyHeaders-issue-tp4825799p4825799.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>


--=20
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/