Except the number 15 (I am afraid that these days there are much less active
JDO implementations) I agree with every word. Things have changed. The
success of JPA might be now in our interest (anyway more than it is in the
interest of Hibernate...).
----- Original Message -----
From: "David Jordan" <[EMAIL PROTECTED]>
To: "Andy Jefferson" <[EMAIL PROTECTED]>
Cc: <jdo-dev@db.apache.org>; "JDO Expert Group" <[EMAIL PROTECTED]>
Sent: Friday, October 06, 2006 11:25 PM
Subject: Re: The Future of JDO
I think we need several thorough, fair and objective, exhaustive lists:
What does JDO have beyond JPA?
What does JDO lack that is in JPA?
Where are the semantic differences between JDO and JPA and can they be
reconciled?
This list should be used by JDO supporters to decide what should be done.
This list should also get published.
On Oct 6, 2006, at 11:02 AM, Andy Jefferson wrote:
I always introduce JPA as a subset of JDO, which is true in terms of
concepts
A while back we compiled a table of the differences (between JDO2 and
JPA1) to
assist users in choosing what they want. You can find it here :-
http://www.jpox.org/docs/persistence_technology.html
The table is not exhaustive (since we only come to features as we
implement
them). For example JPA1 doesn't allow control of specification of
foreign-keys, or indexes whereas JDO2 does - will add this.
I use this table as a basis for defining JPA1 being a subset of JDO2,
and as a
basis for defining what JDO2 requires to be a true superset.
If anyone has items to add to that table we'd be happy to update it.
HTH
--
Andy
