The Artima Developer Community
Sponsored Link

Java Buzz Forum
Scott Crawford on EJB 3.0

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
dion

Posts: 5028
Nickname: dion
Registered: Feb, 2003

Dion Almaer is the Editor-in-Chief for TheServerSide.com, and is an enterprise Java evangelist
Scott Crawford on EJB 3.0 Posted: May 10, 2004 4:27 PM
Reply to this message Reply

This post originated from an RSS feed registered with Java Buzz by dion.
Original Post: Scott Crawford on EJB 3.0
Feed Title: techno.blog(Dion)
Feed URL: http://feeds.feedburner.com/dion
Feed Description: blogging about life the universe and everything tech
Latest Java Buzz Posts
Latest Java Buzz Posts by dion
Latest Posts From techno.blog(Dion)

Advertisement
Scott Crawford has written up his thoughts on the EJB 3.0 process. Scott is an independent member of the EJB expert group, and his thoughts are very interesting. I agree with a lot of the comments that he made in his various articles on the topic, however I do dissagree (of course) with the following: Since I am not a world expert on object persistence but I do want to do the right thing I listen carefully to these arguments. But I also try to take a step back and look at the big picture. A persuasive point for me is to consider the fundamental design goals of JDO and of the O/R tools. One of JDO’s key strengths is that it is datastore-agnostic, meaning your objects persist equally well to OO databases and to relational databases. But trade-offs in design are ever-present and my judgement is that JDO must pay a price for this flexibility. The design goal for EJB 3 is to maximize ease-of-development in our target use case: code running inside application servers using relational databases. Hibernate and TopLink have made some pragmatic, simplifying choices by focusing on this case. I am also influenced by years of community voices speaking positively about their experiences with these two products. I really do not understand how JDO being able to work with different datastores has much to do with anything. JDO 2.0 has been written with the knowledge that the majority of usage of JDO is with relational databases. The majority of vendors have known this... and their OR mapping engines are of a high quality. So, it is incorrect to think JDO == OODBMS anymore. This is simply not true. If the EJB expert group really did discuss JDO, then how come Craig Russell wasn't invited to talk about it? Or any of the other prominent players? If you want to choice between X and Y, surely you talk to the experts on both. I know that a couple are on the EJB group (Gavin, TOPLink), but these are both newbies to the world of JDO (neither on JDO 1). So, I appreciate your comments Scott, I know you made decisions on information that I don't even know about, and I am sure that you did the best job possible. I just still think that it is SUCH a shame that something couldn't have been worked out here. I know the JDO group would have worked hard with you all to make this the best for everyone. And there IS still time. Dion

Read: Scott Crawford on EJB 3.0

Topic: Java Certifications Previous Topic   Next Topic Topic: [Apr 29, 2004 23:17 PDT] 7 Links

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use