EJB provides an object relational mapping mechanism that uses JPA. Many people think Hibernate is based on EJB 3.0, or EJB 3.0 is based on Hibernate, which isn't true, although both technologies pull from many of the lessons learned over the past 5 or 6 years in the industry, and as such, they share a great many similarities.
I like the fact that Hibernate does not need an EJB container to run. This is especially helpful for my WebSphere clients that don't have access to an full version WebSphere EJB 3.0 server. This is always a big concern for clients.
I don't want to barge in on Cameron's parade (sorry, Cameron!), but I just need to clarify Cameron's answer, because I think it was a little misleading (unintentionally, I'm sure).
JPA doesn't need an EJB container any more than Hibernate does (although if you do have a container then JPA is much easier to use than the Hibernate API).
Cameron is quite correct that EJB 3.0 (the JPA part of it) was based on many products and technologies, including but not limited to Hibernate.
Hibernate Annotations does offer some annotation "extensions" (for lack of a better description) that are Hibernate specific, and not part of the EJB 3.0 persistence specification. [ June 04, 2008: Message edited by: Jelle Klap ]
Originally posted by Jelle Klap: Hibernate Annotations does offer some annotation "extensions" (for lack of a better description) that are Hibernate specific, and not part of the EJB 3.0 persistence specification.
[ June 04, 2008: Message edited by: Jelle Klap ]
So what are those annotations ?
Post by:autobot
Bring me the box labeled "thinking cap" ... and then read this tiny ad:
a bit of art, as a gift, the permaculture playing cards