More I mean what bundle(s) should I listen to in order to know that the ClassLoader is no longer valid? Or how would I otherwise know that or be notified of that?
I can ping Christian regarding Aries specifically and get his thoughts. On Wed, May 27, 2015 at 9:16 PM, Brett Meyer <brme...@redhat.com> wrote: > > In regards to OsgiClassLoader and dynamically managing the "classpath", > any > > thoughts on how to handle out single call to > OsgiClassLoader#addClassLoader > > (from OsgiPersistenceProvider passing > > the javax.persistence.spi.PersistenceUnitInfo#getClassLoader we get from > > the e-OSGi container)? > > > > I am not sure what all makes up that ClassLoader. > > Another really good question, but not sure. I *hope* that Aries (and > other Enterprise OSGi JPA providers) would smartly/narrowly scope that to > the specific persistence unit and responsible bundle, but who knows what > that actually means in practice. Since our Enterprise OSGi setup currently > works, I would assume that *some* sort of scoping is in place. Otherwise, > we'd hit CL conflicts. > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
