Where does OSGiBundleManager.stopBundle() emit BundleEvent.STOPPED?

[bosschaert]

In relation to the Start Level Service TCK I am trying to get the following testcase passing:

The test starts a bundle. In the BundleActivator.start() of that bundle it calls a method on the Start Level Service, which under the hood causes the the bundle to be stopped. This potentially happens concurrently, so it's not defined whether the Activator.start() finishes before the bundle is actually stopped or not.

To simplify the test behaviour, I've taken the concurrency out of the picture for the moment. So in my setup, the bundle is actually stopped before BundleActivator.start() is finished.

The TCK test has registered an event listener and expects BundleEvent.STARTED and BundleEvent.STOPPED events. However it never receives the STOPPED event (it does get the STARTED event).

I ended up looking at the OSGiBundleManager.stopBundle() method where the real logic seems to be encapsulated in the following 3 lines:

{code:java}DeploymentUnit unit = bundleState.getDeploymentUnit();
deployerClient.change(unit.getName(), DeploymentStages.CLASSLOADER);
deployerClient.checkComplete(unit.getName());{code}

I don't quite follow how these would stop the bundle and, additionally, where the BundleEvent.STOPPED normally comes from.
Anyone an idea?

[alesj]

DeploymentUnit unit = bundleState.getDeploymentUnit();
deployerClient.change(unit.getName(), DeploymentStages.CLASSLOADER);
deployerClient.checkComplete(unit.getName());

I don't quite follow how these would stop the bundle and, additionally, where the BundleEvent.STOPPED normally comes from.

See OSGiBundleActivatorDeployer.

What this code does it takes unit's undelying MC deployment component and tries to push it to CLASSLOADER stage.

This can be fwd or backwards, depending on the current stage / state.

If it passes the mentioned deployer -- for which OSGiBundleState attachment must exist -- it will trigger that deployer.

[thomas.diesler]

OSGiBundleState.stopInternal

      // This bundle's state is set to RESOLVED
      // A bundle event of type BundleEvent.STOPPED is fired
      destroyBundleContext();
      changeState(RESOLVED);

AbstractBundleState.changeState

         case Bundle.RESOLVED:
         {
            if (previous == Bundle.STOPPING)
               bundleEventType = BundleEvent.STOPPED;
            else
               bundleEventType = BundleEvent.RESOLVED;
            break;
         }

[bosschaert]

I have created a unit test that isolates the issue. It's over here: http://github.com/jbosgi/jbosgi-framework/bundle/src/test/java/org/jboss/test/osgi/service/DeployerTestCase.java