RE: JDO vs JPA

Hello again,
Thanks to all, your responses helped me a lot.
The problem is that we don't have a single project, we have several and they are different to each other.
I guess a good choice is simply use OpenJPA because we will use IBM WAS and everything here is "going relational", but maybe for some projects we will use only pure JDBC if we experience performance issues.
Thanks again

Manuel

-----Mensaje original-----
De: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] En nombre de Thorbjoern Ravn Andersen
Enviado el: sábado, 20 de agosto de 2011 9:11
Para: Java Programming on and around the IBM i
Asunto: Re: JDO vs JPA


Den 19/08/11 11.34, MANUEL FIDALGO SICILIA skrev:

Dear all,

Foremost, I would like to say that I'm new to the AS/400 world so
sorry if I ask stupid things...

At work we are using v6r1m0 and we would to write some Java programs
using the AS/400 as database.

The problem comes when deciding what persistence engine to use: I
can't see clearly if the AS/400 is relational or non-relational and I
would like to know which should be better JPA or JDO. I know some
people use JPA but I'm wondering if it is not better to use JDO which
has support for both relational and non-relational and if JPA will
have performance problems because it is made for relational.

So what do you think? JDO or JPA? Or maybe just jdbc!

First of all: Will you need to access database data created outside your Java program? If yes, you need to look into reverse modelling creating Java objects from database tables. I believe Hibernate has some facilities for this. It also has a DB2/400 dialect.

Then, most O/R mappers want the database to support commit-rollback for
consistency. This may not be enabled for your tables in DB2/400.
This is required for e.g. Hibernate to work.

(and The JDBC driver is in the jt400 jar files.)