Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of cmoulliard@gmail.com
 designates 209.85.220.177 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=V8Zpu35B4pR4zepZkhLMuL0mMhvHmaPTyyftSoTfTQtjCQzSGsQnqmg59rDgbF2fzI
         MgixRtWSrmc38FEeN1k9lziUL7llSS2H3WBvnNtSk/Y2F2QiT9gmRMuFA8uerHmIGwyG
         ysQvroQHyoXJ6lXuvHc1E1nHdd8S1VohQbSkM=
MIME-Version: 1.0
Date: Tue, 19 May 2009 13:59:02 +0200
Message-ID: <a364c40b0905190459o38783d3k8d4ab2694f71e629@mail.gmail.com>
Subject: [Feedback from users] JDO - OODBMS and Camel
From: Charles Moulliard <cmoulliard@gmail.com>
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=0016364163dd0826a5046a42a3c7

--0016364163dd0826a5046a42a3c7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi,

I would like to know if some camel users have already used their favorite
framework with JDO and OODBMS. I contemplate this question because in my
application which is a Straight Through Processing (STP) one, I transform
external data (received from CSV, ... files) into Java Objects which are
later transformed into external format (FIX, Swift, ...). To avoid to have
too much transformation in the STP process (IN to Internal format, internal
format to text, text to internal format, internal format to external format,
...), I think to use the POJOs as internal format of my application and
applying Java to Java transformation to generate my internal/external
format.

Obviously, I must save/store the objects somewhere to persist data in case
of application crash.

Different approaches exist :

1) Export the content of the object into String, XML, ... and save it in a
text/blob field of a RDBMS
2) Save the object in a BLOB field of a RDBMS
3) Save the objects in a OODBMS
4) idem but using JDO specification top of OODBMS, RDBMS

The 1) is very simple to do but required additional transformations from
object to string and string to objects
The 2) seems better because the object is saved in a BLOB. What about
performance ? Is it the bast way to store objects ?
Scenario 3) 4) are interesting but they required a secondary Database (near
my MySQL DB), will complicated the transaction because I have to handle
three components in case of rollback (JMS, RDBMS and OODBMS
The 4) is perhaps mush more interesting because objects are stored in a
RDBMS and JDO is supported by Spring. I can also done queries top of my DB.
Can I use JDO to also perform my SQL queries ? Probably yes but is it
interesting ?

Regards,


Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer

*****************************
blog : http://cmoulliard.blogspot.com

--0016364163dd0826a5046a42a3c7--