Inside Scoop on J2EE : Tips and tricks on J2EE and Oracle Application Server by Debu Panda
Updated: 11/18/2004; 5:19:52 PM.

 

Subscribe to "Inside Scoop on J2EE" in Radio UserLand.

Click to see the XML version of this web page.

Click here to send an email to the editor of this weblog.

 
 

Friday, June 04, 2004

 

 

It is very clear that the JDO expert group is frustrated and is in a panic state after EJB 3.0 expert committee declined to use JDO as the persistence model for EJB 3.0 and made announcement that EJB 3.0 is going to use a POJO based persistence modeled on Hibernate. This fairly apparent from Dave Jordan’s recent article where he tried to scare existing and future EJB customers by providing misleading information about EJB 3.0 that Hibernate is indeed becoming the persistence layer for EJB 3.0 which is not true. I attended EJB 3.0 presentations during the TSS Symposium and spoke to expert committee members and it is clear that EJB 3.0 is adopting features from leading OR frameworks like Hibernate, OracleAS TopLink and NOT just adopting Hibernate as standard as Dave Jordan claims in his article.  He mentioned in the article that Oracle and IBM does not like JDO because they want to protect their database business but tactfully avoided the point that BEA is not a database vendor and they also are also opposed to JDO. Let us not forget that Dave Jordan is a member of JDO expert committee and it is very clear that this article is politically motivated and intended to derail the grand plan of EJB 3.0 of simplification of EJBs because a POJO based persistence model will make JDO irrelevant for mainstream use in J2EE applications.


8:50:20 AM    comment []

© Copyright 2004 Debu Panda.

PS: These are my own thoughts and not of my employer ..



Click here to visit the Radio UserLand website.
 


June 2004
Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30      
May   Jul