Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of hzbarcea@gmail.com designates
 209.85.213.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=iF79xKT/G34cLd1FhwKeg6R2nq/emGSXXvYOfdPXcmLDm28EuYvRb/HIPdnCjTq/Qh
         bHXBY75pW8WNhyAG5NAPisg/GV1oRSQcRcjeCjwcHmCOaUFLgyva27I1fgb+pTLv73T3
         3d/8tdsWykwn67t7V4dIK6UKkgL/ISdscHJYU=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
Subject: Re: Should we (could we?) make Exchanges serializable?
From: Hadrian Zbarcea <hzbarcea@gmail.com>
In-Reply-To: <AANLkTintBySLc=7D0-V10JuB6vth=buQf51L+q9WnRX+@mail.gmail.com>
Date: Fri, 8 Oct 2010 09:51:45 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <952D0425-B7CF-45E4-901B-F7C4C22D7A03@gmail.com>
References: <1286533270197-3204367.post@n5.nabble.com>
 <AANLkTintBySLc=7D0-V10JuB6vth=buQf51L+q9WnRX+@mail.gmail.com>
To: users@camel.apache.org

+1
fwiw, Hadrian

On Oct 8, 2010, at 7:05 AM, Claus Ibsen wrote:

> On Fri, Oct 8, 2010 at 12:21 PM, Ade <adrian.trenaman@googlemail.com> =
wrote:
>>=20
>> 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.
>>=20
>> 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.
>>=20
>> 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.
>=20
> I dont think we should do this. We can not assume the data it contains
> can be serialized.
>=20
> There is a DefaultExchangeHolder class which you can use to serialize
> and Exchange. It has the features to only transfer the objects which
> can be serialized.
> Its used by other components which supports the transferExchange
> options such as camel-jms, camel-mina, camel-netty, camel-hawtdb etc.
>=20
>=20
>=20
>=20
>> --
>> View this message in context: =
http://camel.465427.n5.nabble.com/Should-we-could-we-make-Exchanges-serial=
izable-tp3204367p3204367.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>=20
>=20
>=20
>=20
> --=20
> Claus Ibsen
> Apache Camel Committer
>=20
> Author of Camel in Action: http://www.manning.com/ibsen/
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus