Re: [equinox-dev] Auto starting/stoping "normal" OSGi bundles on eclipse

[Rafael Chaves <Rafael_Chaves@xxxxxxxxxx>]

Right now, the trigger is a "Legacy:
true" entry in the bundle manifest, but it is going to be one of the
attributes for the new Eclipse-automation entry:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=52393

If your bundle does not have the "Legacy:
true" entry, and your bundle is being automatically stopped on shutdown,
it would be a bug.

Rafael

Thomas Watson <tjwatson@xxxxxxxxxx>
Sent by: equinox-dev-admin@xxxxxxxxxxx

03/03/2004 08:47 AM

Please respond to
equinox-dev

To	equinox-dev@xxxxxxxxxxx
cc
Subject	Re: [equinox-dev] Auto starting/stoping "normal" OSGi bundles on eclipse 3.0

I should have tested this on the latest code.  It seems to be working
as expected.  :-) 

Normal bundles do not seem to auto stop.  What is the trigger to auto
stop a bundle anyway? 

Thomas Watson

Thomas Watson/Austin/IBM@IBMUS Sent by: equinox-dev-admin@xxxxxxxxxxx 03/03/2004 07:36 AM Please respond to equinox-dev

To:        equinox-dev@xxxxxxxxxxx        cc:                Subject:        [equinox-dev] Auto starting/stoping "normal" OSGi bundles on eclipse 3.0

I am attempting to use pre-existing OSGi bundles with the equinox runtime.
 I find that everything seems to work fine when I install and start
a "normal" OSGi bundle on Equinox.  But when the equinox
runtime is shutdown core.runtime ends up stopping all the bundles.  On
next startup my bundles are still installed but are not active.  I
then have to start the bundles my self again.  This is not expected
behavior for "normal" OSGi bundles.  These bundles expect
to be started if they were active at the time the Framework was shutdown.
 Is there a way to prevent this from happening?  Should there
be an eclipse header that runtime looks for when determining whether a
bundle needs auto stopping?  I think right now it only auto stops
bundles that have a Bundle-SymbolicName. 

Thomas Watson