This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Isn't it easier to think of it this way: JPA 2.0 is a specification, while OpenJPA and Hibernate are implementations of the specification?! And as a consequence..you can't use JPA 2.0 since it's just a specification, you have to use an implementation of it, and you can pick either OpenJPA or Hibernate.
thanks....wil do some resch between OpenJPA 2.0 and Hibernate.thanks clarification.
Joined: Feb 02, 2009
My advice would be to use only JPA 2.0 features if possible. In this way you can easily port you application between different implementations (and runtime contains which have bundled different implementations of JPA 2.0).
It means, stop comparing OpenJPA 2.0 and Hibernate, write business functionality, and only compare if you need some very specific optimalizations/extensions made by either of the providers.