Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

EKB 3.0 and Hibernate Similarities in the Book of EJB 3.0

 
Durrab Jami Khan
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Mike Merrick,

When I was doing the Hibernate studies then some how I knew that EJB 3.0 will have some features of Hibernate and my question is:

. Is EJB Similarities with Hibernate discussed in this book.

. If not then is there any comparison so we can preffer EJB 3.0 over Hibernate

Thanks & Regards:

Durrab Jami Khan

Cell: +92-333-4715789
 
Mike Keith
author
Ranch Hand
Posts: 304
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

The persistence part of EJB 3.0 (JPA) is based off of all of the successful O/R mapping products and includes the most frequently-used features from Hibernate, TopLink, and JDO-based products. All of the persistence features in the spec are discussed in detail in the book. The advantages to using JPA over any particular O/R mapping product are the same as using any standard over a proprietary product. You are reducing your risk, increasing the portability of your application, amongst a whole host of other benefits. We discuss this in more detail in chapter 1 of the book.

Regards,
-Mike
 
Ram Gokul
Ranch Hand
Posts: 85
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Mike !
It is a valid argument that Toplink / hibernate is more proprietry and hence we will be tied to their product when upgrading / porting to our client sites .

I had asked this in another post . I will post it here so that there is a continuity on the subject.

"For projects that are in begining stage which of these 2 approaches do you advice ?. " ( apart from portability issue ).
 
Mark Spritzler
ranger
Sheriff
Posts: 17278
6
IntelliJ IDE Mac Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It is only when you use the propriatary extensions of Toplink or Hibernate that you get the portability issues. If you use the base JPA APIs, you can still use the Toplink or Hibernate implementations of the Spec and be completely portable.

As Mike had pointed out, the spec to the most popular features of the ORM products that are out there and basically bumped them up to a specification level, so that only in the "rare" cases that use the features of an ORM product that isn't used as much, you tie yourself with the vendor.

Mark
 
Erik Bengtson
Ranch Hand
Posts: 90
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
and be completely portable.


Theorically yes, however the spec is under specified and TCK does not cover all. Pratically, you are API portable but not behavioral.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic