[hibernate-dev] Ejb3Configuration
Steve Ebersole
steve at hibernate.org
Wed Jul 11 11:02:53 EDT 2012
We all have agreed that Ejb3Configuration is a mess. In my JPA 2.1
branch I again decided to look at attacking that problem. So I came up
with the notion of an EntityManagerFactoryBuilder that takes the place
of Ejb3Configuration.
That code is all in place and all tests that use JPA boostrapping
through Persistence or PersistenceProvider are passing. I still have
not changed the base test classes that build an Ejb3Configuration as
means to bootstrap HEM, so I am not sure how much of that logic is
missing. The reason I stopped is that what I REALLY want to do is to
just rip out Ejb3Configuration. We deprecated it back in 4.0 for just
this purpose. We knew that we wanted to replace it and that
Ejb3Configuration would simply not work when we went to integrate
metamodel. EntityManagerFactoryBuilder is built to work with the new
metamodel code.
So bottom line, unless I hear compelling reason(s) not to, I plan on
removing Ejb3Configuration from the codebase. The sooner the better.
--
steve at hibernate.org
http://hibernate.org
More information about the hibernate-dev
mailing list