Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.216.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=vtCPifkYDnhJOB+8DkPmKWyW47xMM5XvNwy2Bq76WEmtQya6A0uPcULhuuf8IwPCuR
         9iau3ml4I7Ka6dr8GaldrmCvyz2JR/1gXFOX1SwAlG3AfLhVMUlikuHWFCQZmLfoNLOE
         WxItrL8bWXwl3FPzL7lb7KwMsc5iD1nqQUIe0=
MIME-Version: 1.0
In-Reply-To: <AANLkTimdON5ppyndNdoffTYdDtdLyLZnarh4TjkGXEGs@mail.gmail.com>
References: <1300914833654-4259599.post@n5.nabble.com>
 <4D8AF539.7010508@gmail.com>
 <1301005391184-4263203.post@n5.nabble.com>
 <AANLkTikrkQvrHUt1vVWpOFELAOLk+KMn=Ymn_jFCL4HH@mail.gmail.com>
 <AANLkTimdON5ppyndNdoffTYdDtdLyLZnarh4TjkGXEGs@mail.gmail.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Fri, 25 Mar 2011 11:44:42 +0100
Message-ID: <AANLkTimGTft1x7SdYXMtuRCG55D8FcwyxnG=wirR0cn5@mail.gmail.com>
Subject: Re: choice when check BodyType:null, Body:null
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, Mar 25, 2011 at 3:42 AM, Tim <chengt@gmail.com> wrote:
> so based on the cause of that bug, it is impossible to set the body of
> a jms message to null even if it was transformed earlier.
> So for example if you had:
>

Its not a bug, thats how it was designed.
Its very unusual to route null messages.

You should most likely be able to do a
exchange.setIn(new DefaultMessage());

Or something like that to work around your issue.


> jmsmessage (a) -> bean which returns (b) based on that message -> bean
> c which returned null based on b -> bean d.. d would get (a) again.
> (note that it doesn't even get b which was after a).
>
> On Thu, Mar 24, 2011 at 9:38 PM, Tim <chengt@gmail.com> wrote:
>> I believe you ran into https://issues.apache.org/jira/browse/CAMEL-3354
>>
>> On Thu, Mar 24, 2011 at 5:23 PM, Eric East <eaeast@yahoo.com> wrote:
>>> Thanks for response.
>>>
>>> I narrowed down my test case where I see the issue.
>>>
>>> When I initiate a route using a jms activeMQ broker (internal VM), the
>>> exchange.setBody(null) does not set the body to null.
>>>
>>> I am using Camel 2.5. =A0Actvemq 5.4.1
>>>
>>>
>>> TEST CASE FAILS:
>>> template.sendBody("activemqVM:topic:tlm", SomeObject);
>>> from("activemqVM:topic:tlm").to("direct:one")
>>>
>>> TEST CASE WORKS:
>>> template.sendBody("direct:one", SomeObject);
>>>
>>>
>>> ROUTE
>>> from("direct:one")
>>> .log("processing ${in.body}")
>>> .process(new Processor(){
>>> =A0 =A0 =A0 =A0public void process(Exchange exchange)throws Exception{
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0exchange.getIn().setBody(null);
>>> =A0 =A0 =A0 =A0}
>>> })
>>> .log("new body: [${in.body}]")
>>> .choice()
>>> =A0 =A0 =A0 =A0.when().simple("${in.body} !=3D null")
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0.log(" !=3D null")
>>> =A0 =A0 =A0 =A0.otherwise()
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0.log(" =3D=3D null");
>>>
>>> --Eric
>>>
>>>
>>>
>>> --
>>> View this message in context: http://camel.465427.n5.nabble.com/choice-=
when-check-BodyType-null-Body-null-tp4259599p4263203.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
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/