|Bundle Activation question [message #111473]
||Tue, 03 June 2008 15:48
Originally posted by: techi_amol.yahoo.com|
I had a doubt about bundle activation. I have been reading the sections
about lazy activation policy in osgi spec and i am a little confused.
1) What is the difference between Bundle Activation and calling
2) Does bundle activation mean loading of all classes that are there in
3) I was assuming that is BundleActivation policy is not set to lazy the,
on deployment the BundleActivator.start() method will be called
automatically by the framework, but it doesn't happen that way.
|Re: Bundle Activation question [message #111690 is a reply to message #111473]
||Tue, 10 June 2008 09:47
| Kees Pieters
Registered: July 2009
OSGI tries to start bundles automatically, so normally you do not want to be calling the BundleActivator.start(). If you do experience that bundle does not start, then this usually means that something is wrong. you can check this by entering 'ss' in your console (dos command prompt or in Eclipse) after you started the application. your bundle should be ACTIVE. If not, the entering 'diag <plugin number/name>' will normally provide additional information to what went wrong.|
Lazy activation mainly has to do when there are plugin dependencies. Setting lazy-start true, will tell OSGI that the plugin should be loaded only when others need it. In your runtime configuration (or in the config.ini file when you start OSGI manually), you normally define that OSGI starts your main plugin, after which the system loads the others if needed. Lazy activation supports this.
Powered by FUDForum
. Page generated in 0.03086 seconds