equinox-dev-bounces@xxxxxxxxxxx wrote on 09/11/2006
> Grzegorz Glowaty wrote:
> > PackageAdmin specification says that it will refresh all the
> > that are either updated or depending on updated bundles. It is
> > to be included in the graph build by PackageAdmin for a bundle
> > refreshed. This must cause assignement of a new classloader to
> > bundle. If such a bundle (not updated directly, but refreshed
> > one of the bundles it relied on was updated) contains a native
> > it will result in JVM error stating that the library was loaded
> > another classloader. Is there any way of preventing this?
> > Oscar (objectweb osgi impl) does a nice trick of renaming the
> > directory upon refresh (not only upon update). This causes the
> > to change disk location, thus to be able to be loaded by another
> > classloader. Is there something similar built in into equinox?
> > Currently we are observing the mentioned error which worries
> > it is not. If it is not, maybe it would be worth adding?
> This is carried over into Felix too.
Hi! Any other thoughts on it? Any side effects or implications of the approach above that would prevent from going this way? I opened a bug in bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=139064
I expect that this may be a big change to the code
as probably something like BundleRefresh implementing BundleOperation will
I could help implementing but some guidence on the
design would be appreciated just to know where these kind of things
Best regards / pozdrowienia,