|Re: Bundle update and buddy classloading [message #334986 is a reply to message #334961]
||Fri, 13 March 2009 16:40
| Paul Webster
Registered: July 2009
Laurent Dubois wrote:|
> I'm having some trouble with buddy classloading after a bundle update
> (where the classpath gets updated) and wondering if I'm missing something.
> my setup is:
> - bundle A with a registered buddy policy
> - bundle B with a registered buddy A
> then bundle A gets updated (new classpath), but bundle B does not "see"
> the change when looking for a class that is part of the newly updated
> classpath in bundle A.
> A loadClass() call on bundle A directly gets the class, but not from
> bundle B...
> so my question is: Does a bundle update automatically triggers a
> classloading update on the registered buddy, or I have to do something
> specific (and how)?
You're more likely to get info from eclipse.technology.equinox, so I've
marked that for follow up.
Depends on what you mean buy bundle update? If you use OSGi to stop a
bundle, install a new version, and start that one you also need to use
the PackageAdmin service to refresh packages that are exported, etc.
If you mean an update (Update Manager or p2) that you then restart
eclipse, it should have restarted with the new classpaths, no?
Powered by FUDForum
. Page generated in 0.01590 seconds