[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [equinox-dev] OSGi new startup policies
|
Jeff McAffer wrote:
>
> This is a good thread. It would seem that we will have some
> compatibility issues to work through. Of course, if someone has
> Eclipse-LazyStart then we can still start them automagically. For
> people looking to get on the new/standard header though we should make
> it possible/easy.
>
> Perhaps there should be a bug opened to track this? (what release/build
> should we target for the changes?) Here are some random thoughts about
> the scope of change
> - bundles installed by update.configurator
> - bundles installed by osgi.bundle
> - people looking at the state of bundles to decide what to do (e.g.,
> some people were previously looking and starting the bundle if it was in
> Resolved state). Now they will not get quite what they
expected/wanted...
If the bundle is RESOLVED and they want it started, call
start(START_TRANSIENT).
If the bundle is STARTING|ACTIVE then the bundle is already started and
nothing needs to be done.
This is the same as before (except they can now use START_TRANSIENT to
avoid altering the persistent autostart setting.)
>
> Jeff
>
>
BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance
hargrave@xxxxxxxxxx
office: +1 386 848 1781
mobile: +1 386 848 3788