camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marco Zapletal <>
Subject Re: Using properties or headers to persist meta information on the exchange?
Date Wed, 08 Jun 2011 16:36:16 GMT

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 exception, which cancels the 
execution of the process instance.


On 08.06.2011 18:26, Claus Straube wrote:
> 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
>> (
>> 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 endpoints).
>> I would like to know whether this in principle correct. If so, I ran
>> into the problem that properties seem to stripped away if an exchange
>> goes through a JMS queue. Could anyone tell me what's the recommended
>> approach to keep meta information durable on the exchange.
>> thanks,
>> marco

View raw message