• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

article comparing Java ORM frameworks

 
Rancher
Posts: 43081
77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
java.net just published an article comparing some of the major contenders in the Java ORM space (EJB, JPA, Hibernate, TopLink): http://today.java.net/lpt/a/464
 
ranger
Posts: 17347
11
Mac IntelliJ IDE Spring
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Unfortunately, I think that article does more harm, and introduces more confusion to newbies, because it looks like the 4 listed are seperate products and do not overlap. That is a problem, because both Toplink and Hibernate implement the JPA spec. Many people think that if they choose JPA, they can't use Toplink or Hibernate, which is incorrect.

So I saw this under the Hibernate sections
"You need container-provided services, such as those provided by EJB, in which case your choices are pretty much limited to EJB."

Well, if you are using Hibernate's version that also implements the JPA spec, and run it inside a App Server, you get all the container-provided services. Even before, when you ran beginTransaction in Hibernate's sesssion api, Hibernate was smart enough to see if JTA was there and join the JTA Transaction of the EJB Container.

So, I would be more concerned with the misconceptions that that article presnets, and would much rather people know that there is a lot of flexibility in what you can choose to use.

Mark
 
reply
    Bookmark Topic Watch Topic
  • New Topic