Claus, thanks for your response. yes, it is quite obvious that in such
cases, the headers will be lost (which would be the case for properties,
too). I was just a little bit confused about the distinction between
headers and properties, after reading the thread I cited [1].
Anyway, I will stic
Marco, I think it depends on what you want to do. Of course there're
components where you will loose message headers. Look at the file
component, hazelcast:map or a database component. Of course you'll loose
here the message headers, because they're bound to camel (where should
you store them i
Does that mean you can't count on your custom Camel message headers to
survive a transition to JMS?
> -Original Message-
> From: Claus Ibsen [mailto:claus.ib...@gmail.com]
> Sent: 08 June 2011 19:41
> To: users@camel.apache.org
> Subject: Re: Using properties or hea
Yes, I've read that. Actually, I just wanted to keep my (String)
properties when the exchange goes through the JMS queue (similar like
headers are kept over JMS queues).
If it is the intended behavior that exchange properties are stripped
away by the JMS component, I am fine with using headers
The JMS spec limits what can be send as JMS headers. Read more details
on the Camel JMS wiki page. And for example in the JMS java doc.
On Wed, Jun 8, 2011 at 6:36 PM, Marco Zapletal wrote:
> Hi,
>
> thanks for the quick response. Yes, I've tried this, but this opens up
> another problem if you
Hi,
thanks for the quick response. Yes, I've tried this, but this opens up
another problem if you use a CXF endpoint on your route. The CXF
endpoint seems to store an instance of
org.apache.cxf.service.model.MessageInfo on the exchange, which is not
serializable. This results in a runtime exc
Hi Marco,
have you tried 'transferExchange=true' inside your JMS route? That could
be a solution for your JMS problem.
Best regards - Claus
On 08.06.2011 18:23, Marco Zapletal wrote:
Hi,
I learned from this thread
(http://camel.465427.n5.nabble.com/How-long-do-the-camel-headers-live-in-rou
Hi,
I learned from this thread
(http://camel.465427.n5.nabble.com/How-long-do-the-camel-headers-live-in-routes-td474477.html)
that one should use properties instead of headers in order to durable
store meta information on an exchange (acc. to one of the postings,
headers can get lost at endpo
