| lazystart and BundleActivator.start(BundleContext) [message #313182] |
Tue, 06 March 2007 10:30  |
Eclipse User |
|
|
|
I'm wondering exactly how you're supposed to call the
BundleActivator.start(BundleContext) method manually.
This is my situation:
PluginA
- Eclipse-LazyStart: false
PluginB
- Eclipse-LazyStart: true
- Depends on PluginA
PluginB must set properties in PluginA in order for PluginA to start()
propertly. After I set the properties, how do I go about propertly calling
PluginAActivator.start(BundleContext)? What do I need to pass in for the
argument BundleContext?
Thanks in advance,
Albert
|
|
|
| Re: lazystart and BundleActivator.start(BundleContext) [message #313761 is a reply to message #313182] |
Mon, 26 March 2007 09:35  |
| Eclipse User |
|
|
|
Albert Huh wrote:
> I'm wondering exactly how you're supposed to call the
> BundleActivator.start(BundleContext) method manually.
>
> This is my situation:
> PluginA
> - Eclipse-LazyStart: false
>
> PluginB
> - Eclipse-LazyStart: true
> - Depends on PluginA
>
> PluginB must set properties in PluginA in order for PluginA to start()
> propertly. After I set the properties, how do I go about propertly calling
> PluginAActivator.start(BundleContext)? What do I need to pass in for the
> argument BundleContext?
>
1) that's not a good dependancy tree, if B needs A, but A can't start
without information from B ... what about creating A, B, and Ba, where A
needs Ba which can set the preference.
2) you can manually start a plugin by looking up the Bundle (I use
Platform, although there's a better way in 3.3) and calling Bundle#start().
3) if you manually start a bundle, it will be auto-restarted the next
time eclipse starts back up ... you either have to be prepared for that
in plugin A (save the prop in your state location) or make sure you stop
it on the way out.
PW
|
|
|
Powered by
FUDForum. Page generated in 0.03398 seconds
Home