I would like to get the benefit of auto-discovery of my annotated classes by using JPA, but I'd prefer to continue using hibernate as usual (i.e. SessionFactory and HQL).

I have seen hints that I can simply configure a LocalContainerEntityManagerFactoryBean (in Spring) and then alias the session factory from getSessionFactory(). However this method doesn't seem to exist in those interfaces.

I see a more circuitous route where I get an entity manager's delegate and cast it to a SessionImplementor, but that doesn't feel right.

Is using JPA just to get auto-discovery a reasonable thing to do or do I just have to live with no auto-discovery of classes to use regular hibernate?

Why on earth hasn't somebody added whatever discovery code is used for JPA to the hibernate annotations core? Is use of native hibernate now discouraged? (Should I just move on?)


thanks,
Pat

Well, the answer seems to be to blindly follow the hints I saw:

<bean id="sessionFactory" factory-bean="entityManagerFactory"
factory-method="getSessionFactory" />

But I still don't understand how that works, as that method doesn't seem to exist on the entity manager and the class doesn't seem to be proxied or intstrumented. There must be something I'm missing.


Pat

Hi,

you just have to note that with hibernate as a JPA-Provider, the EntityManagerFactory (which is in fact an Interface) is an Instance of HibernateEntityManagerFactory - which is more or less a wrapper around a Session Factory. So you just do something like this:

Could anyone explain me, how does the entityManagerFactory bean changes from org.springframework.orm.jpa.LocalEntityManagerFactoryBean to org.hibernate.ejb
Class EntityManagerFactoryImpl?