[news.eclipse.platform.rcp] Re: How to force a call to plugin's start()

[Matt Hegarty <mash_909@xxxxxxxxxxx>]

Hmm - well I removed the call to bundle.start() and it still worked ok.
So I guess calling:

  Platform.getBundle(namespaces[i]);

Is enough to cause the guest plugin's Activator to start.

Matt Hegarty wrote:
> Thanks for the responses.
>
> Alex - The reason I can't follow your suggestion is because of the way I 
> have designed my app - namely the Master plugin doesn't know about the 
> classes in the guest plugins.  It would be ideal if the guest plugins 
> would just start after the Master plugin.
>
> David - I'll look into your suggestion.
>
> To be more specific, within my Master plugin's Activator I have a simple 
> List, the contents of which are displayed in a TreeViewer.  I would like 
> guest plugins to be able to get a reference to the List and add objects 
> which are then rendered in the Tree.
>
> Matt
>
> Alex Blewitt wrote:
> > You shouldn't start() it -- the start/stop level of a bundle is 
> > managed by the OSGi framework, not you. What you're seeing is an error 
> > when the bundle in question is either started or starting.
> >
> > What you should do is just access the class(es) that you want; if you 
> > have Eclipse-LazyStart: true then it will bring your bundle up on 
> > first access.
> >
> > Alex.