not right now...We still need to define how EntityManager can be identified as well just finish the specification before we can get to how this integrates with Hibernate.
Can you give more detail to your requirements here on forum? AFter a bit of discussion we'll schedule it for another preview release.
I have played around some and there're a few things to add.
The first problem is that Hibernate-Annotate and EJB3 are using diffrent classes for annotations (ejb.* vs persistence.*) as well as diffrent versions of Hibernate - but this will go away when things gets a bit more stable.
Currently to avoid some problems I have to build an ear file with one ejb3 archive that has a Class-Path to a jar with the Hibernate POJOs. To this jar I have also added classes from the HAR deployer to join the Hibernate Session to the Transaction.
In the future I guess it will be possible to deploy ejb3 with the ejb3 deployer and the Hibernate classes with the HAR deployer (as soon as there's a version for hb3). Maybe this is the gernerall long term solution?
For me this is not good enought since I need to rebuild the SessionFactory at runtime from time to time - but this will also be a lot easier when all componens are using the same versions of the Annotations and Hibernate.
For me it would be nice if I could add Hibernate Annotated Entitys to the ejb3 archive without them beeing picked up by the EJB3 EntityManager.