It's possible because Hibernate _implements_ the EJB 3.0/Java Persistence standard. So
by definition it has to offer a superset of features. EJB 3.0/Java Persistence is needed
because it is an industry standard of a subset of Hibernate features.
If you are looking for things that Hibernate can not do but that Java Persistence can not
do, you will not find any. But it's also not useful to compare a product with a
specification, compare product with product.
Seam offers easy access to the Hibernate feature superset (in addition to making EJB 3.0
standard features easier available). Read up on the Seam managed persistence contexts in
the doc, you can use either EntityManager or Hibernate Session API with that.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029130#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...