Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-user@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <12902524.post@talk.nabble.com>
Date: Wed, 26 Sep 2007 07:44:44 -0700 (PDT)
From: schlemmi <schlemminger@planet-ic.de>
To: camel-user@activemq.apache.org
Subject: Re: Message Properties not forwarded with Camel Activemq Component?
In-Reply-To: <ec6e67fd0709260625w4733f763lf0f616ff8872d900@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <12900714.post@talk.nabble.com>
 <ec6e67fd0709260625w4733f763lf0f616ff8872d900@mail.gmail.com>


James,

Thanks for the response,

>> I used it since 4 weeks with activemq and the lingo library.
>
>Great! BTW I've been slowly working on integrating most of the Lingo
>library functionality now; so you can use Camel to do custom
>transformations or smart routing, or just use JMS or any other
>transport just as easily as Lingo...
>
>http://activemq.apache.org/camel/bean-integration.html
>
>so eventually, when we've got all the features implemented, Camel
>could be a replacement for Lingo offering more features & being more
>flexible.

I use some features from the bean component and I think I can kill the
library
on the server side...

>
>> the log for the send message:
>> ---

>Are you positive thats not just a logging issue. (ActiveMQ only
>deserializes the properties lazily; so they don't necessarily always
>appear in a log statement AFAIK).

You are right, this is a logging issue. I can route with the header.
Apparently I need advanced training in message selectors and headers...

--
 Andreas
-- 
View this message in context: http://www.nabble.com/Message-Properties-not-forwarded-with-Camel-Activemq-Component--tf4522311s22882.html#a12902524
Sent from the Camel - Users mailing list archive at Nabble.com.