Bram, et al. So I have added this as one of my tasks for after my 5.0 release. There are currently 2 hibernate-osgi related tasks tentatively scheduled for 5.1; if any one had thoughts, suggestions feedback on them that would rock :)
https://hibernate.atlassian.net/browse/HHH-9818 https://hibernate.atlassian.net/browse/HHH-9819 Additionally, one will affect Aries to a degree: https://hibernate.atlassian.net/browse/HHH-9822 Anyway, in regards to HHH-9818 what I plan to do is to: 1) segment the contributions to OsgiClassLoaderService by the bundle that provides them 2) register BundleListener for all bundles that contribute to OsgiClassLoaderService 3) handle bundle events by "managing" the segments of the OsgiClassLoaderService Please correct me now if I am way off base so far :) The one thing though that really concerns me is enterprise cases (Aries, etc) and PersistenceUnitInfo#getClassLoader. I know Enterprise OSGi's JPA spec deviates some from the Java EE JPA spec, so I wanted to better understand how this piece works in Enterprise OSGi JPA or even just in Aries JPA. Does Aries JPA return a ClassLoader on calls to PersistenceUnitInfo#getClassLoader? And if so, how can a provider know when that ClassLoader is no longer valid in part or in total (because one or more bundles that comprise it have gone away, e.g.)? -- View this message in context: http://karaf.922171.n3.nabble.com/Hibernate-OSGi-Integration-tp4040190p4040611.html Sent from the Karaf - User mailing list archive at Nabble.com.
