camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adrian Trenaman <trena...@progress.com>
Subject Re: Should we (could we?) make Exchanges serializable?
Date Fri, 08 Oct 2010 12:00:30 GMT
  Thanks Claus for the quick response! Will propose the 
'transferExchange' approach.

Cheers,
Ade.

On 08/10/2010 12:02, Claus Ibsen wrote:
> Hi
>
> There is a transferExchange option on the JMS component
>
>
>
> On Fri, Oct 8, 2010 at 12:21 PM, Ade<adrian.trenaman@googlemail.com>  wrote:
>> I've never been a fan of Java serialization; however, I've been working with
>> a Camel user who wants to be able to serialize an exchange and place the
>> whole thing on a JMS queue. The motivation is that they want to set the
>> exchange up to be subsequently persisted in a database for audit purposes,
>> but they want to separate the writing to a queue (relatively fast and
>> asynchronous) from the act of persisting to a database.
>>
>> In order to achieve this, they've had to create their own serializable
>> versions of Exchange, Header, Property, Message and Attachments. This works,
>> but it's painful to have to write and maintain that extra code.
>>
>> So. Just curious: would it be possible to modify the Camel core API and make
>> Exchanges etc. serializable? Interested to hear people's thoughts on this.
>> --
>> View this message in context: http://camel.465427.n5.nabble.com/Should-we-could-we-make-Exchanges-serializable-tp3204367p3204367.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>
>

Mime
View raw message