Hi Steve, A while ago I've created an alternative hibernate OSGi integration while working on Amdatu JPA [1] because the OsgiClassLoader in hibernate-osgi is causing problems when updating persistence bundles. This approach is inspired by the work of Peter Kriens [2] which makes Hibernate work by managing the TCCL. We currently have hibernate support available for Amdatu JPA based on this approach as an Amdatu Labs project [3].
I've now applied this to the hibernate-osgi integration itself [4], I think it needs some extra work on the native part as there are no wrappers for Session(Builder) yet. Before I start working on this I'd like to know if you expect issues with this approach and if you think this is an improvement to the current OSGi support. Regards, Bram 1: http://amdatu.org/components/jpa.html 2: https://github.com/osgi/bundles/tree/master/osgi.jpa.managed/src/osgi/jpa/managed/hibernate/adapter 3: https://bitbucket.org/amdatulabs/amdatu-jpa-hibernate 4: https://github.com/hibernate/hibernate-orm/pull/958 On Fri, May 15, 2015 at 5:39 PM sebersole <[email protected]> wrote: > cschneider wrote > > I found that restarting the hibernate osgi bundle made it work again. > Does > > this mean this is a problem with classloading in hibernate? > > It is essentially what I alluded to before. Specifically, assuming you use > 4.3 or 5.0, what you see specifically boils down to > org.hibernate.osgi.OsgiClassLoader and > org.hibernate.osgi.OSGiClassLoaderServiceImpl and the fact that these are > not rebuilt when the "requesting bundle" changes. Feel free to contact me > about ways to accomplish that > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Hibernate-OSGi-Integration-tp4040190p4040384.html > Sent from the Karaf - User mailing list archive at Nabble.com. >
