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.
