[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
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 Member, IBM
OSGi Fellow and CTO of the
OSGi Alliance

office: +1 386 848 1781
mobile: +1 386 848 3788

From: "Kirchev, Lazar" <l.kirchev@xxxxxxx>
To: "equinox-dev@xxxxxxxxxxx" <equinox-dev@xxxxxxxxxxx>
Date: 2010/04/14 08:21
Subject: [equinox-dev] Starting the system bundle
Sent by: equinox-dev-bounces@xxxxxxxxxxx

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