Yes, you should use the FrameworkEvent.STARTED event for this. You should probably open a bug so we can investigate the current behavior anyway to see if the comment is valid.
Tom
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|BJ Hargrave/Austin/i...@ibmus
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Equinox development mailing list <equinox-dev@eclipse.org>
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|04/14/2010 08:14 AM
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Re: [equinox-dev] Starting the system bundle
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
We don't you just wait for the FrameworkEvent.STARTED event?
* This event is fired when the Framework has started after all
installed
* bundles that are marked to be started have been started and the
Framework
* has reached the initial start level. The source of this event is
the
* System Bundle.
--
BJ Hargrave
Senior Technical Staff office: +1 386 848
Member, IBM 1781
OSGi Fellow and CTO of the mobile: +1 386 848
OSGi Alliance 3788
hargr...@us.ibm.com
From: "Kirchev, Lazar" <l.kirc...@sap.com>
To: "equinox-dev@eclipse.org" <equinox-dev@eclipse.org>
Date: 2010/04/14 08:21
Subject: [equinox-dev] Starting the system bundle
Sent by: equinox-dev-boun...@eclipse.org
Hello,
We are implementing logic which depends on the system bundle being put in
ACTIVE state after all bundles, which should be running, are started.
However, it turned out that actually the system bundle is put in ACTIVE
state just before the bundles are started. This is evident from the method
StartLevelManager.doSetStartLevel(…), which is called from the
EquinoxLauncher. There is a comment in the code, that putting the bundle in
ACTIVE state “should be done just before firing the STARTED event for the
system bundle” but is done earlier, because “some depend on the system
bundle being in the ACTIVE state when they are starting”. Do you think it
is possible to change the current behavior and put the system bundle in
ACTIVE state after the other bundles are started, as it is in the OSGi
spec?
Kind regards,
Lazar Kirchev_______________________________________________
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
<<inline: graycol.gif>>
<<inline: ecblank.gif>>
_______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
