Here is an excerpt (note that follow-ups posts say it may be inaccurate).
Good luck sorting this out!
Don
============================
Politically Charged EJB Decision Hands a Victory to JBoss
Posted By: Antonio Gallardo on June 03, 2004 @ 07:05 AM
The EJB expert group's decision to use Hibernate as the persistence mechanism in EJB 3.0 gives JBoss all the power. David Jordan, a member of the JDO expert group, explains why the JDO community is not just disappointed�but concerned�about a power shift in the app server market.
Excerpt:JDO Isn't Just for Object Databases
Since the JDO 1.0 release, JDO has gained about 20 relational and three object database implementations. Most of the JDO applications being developed today are targeted for use with a relational database. However, the EJB community is trying to marginalize JDO by associating it with object databases:
Ed Cobb, VP of Architecture & Standards at BEA, voted against JDO, saying its "market acceptance is essentially constrained to use with object databases."
Oracle also has been telling everyone that JDO is only for object databases. During last year's JavaOne conference, I attended a presentation titled "Container Managed Persistence: Beyond the Specification" in which Oracle's Sastry Malladi told his audience the same thing.
At the recent May meeting of the Triangle Java User's Group in Research Triangle Park, N.C., Gavin King, the architect of Hibernate, stated that JDO is "a solution for flat files and object databases�and, oh yes, there are a few relational implementations too." As a participant in the JDO 2.0 expert group, King knows there are many relational JDO implementations.
At this same meeting, Marc Fleury presented a slide stating "Hibernate is focused on ORDBMS, unlike JDO."
_______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
