Hi Bram. Sorry I do not get notified of replies here for some reason, even though I subscribed to the mailing list as well.
I think this approach is based on older versions of Hibernate. As we have said all along OSGi support in Hibernate 4.2 was a first step, but not really ready for prime time. In definitely got better in 4.3 which is what the Karaf integration is based on I believe. It is better still in 5.0 which is what I am working on atm. The work in 4.3 was really about removing code in Hibernate that relies on TCCL and migrating to rely on the idea of a ClassLoaderService which is based on an idea of services that I had been working on for quite some time. So in 4.3 very little, if any, Hibernate code uses TCCL calls. However, we do certainly have some libs which we know use TCCL. 5.0 addresses the rest of TCCL issues, including in the main culprit lib.. hibernate-commons-annotations. Ultimately I want to replace hibernate-commons-annotations with Jandex and some other stuff, but that was not going to fit in 5.0. So what I did instead was to change hibernate-commons-annotations to accept help in class loading and I hook into that from Hibernate delegating to our ClassLoaderService. Sorry for the history lesson :) Anyway, I would really need convinced that your pull request is the direction to go for Hibernate 4.3 and 5.0 -- View this message in context: http://karaf.922171.n3.nabble.com/Hibernate-OSGi-Integration-tp4040190p4040394.html Sent from the Karaf - User mailing list archive at Nabble.com.
