Adrian Brock [http://community.jboss.org/people/adrian%40jboss.org] replied to the discussion "On demand resolution" To view the discussion, visit: http://community.jboss.org/message/534854#534854 -------------------------------------------------------------- It's happening because B's deployment unit has required-stage of "CLASSLOADER" (RESOLVED in OSGi) after the start() failed. i.e. it wants to resolve it. So when you install bundleX, it also says, hey B is not in the correct state and I can resolve it now, but only by moving X to ClassLoader as well. That is what lazy resolve is all about. It automatically resolves other classloaders that it needs if they are not resolved. If B went back to required-stage "DESCRIBE" (INSTALLED in OSGi) after the start() failed then your test would work as expected. I worked this out by adding the following to the test after the b.start() failure:          OSGiBundleState bs = (OSGiBundleState) getBundleManager().getBundleState(bundleB);          System.out.println(bundleB.getSymbolicName() + " state=" + ConstantsHelper.bundleState(bundleB.getState()) + " required=" + bs.getDeploymentUnit().getRequiredStage()); Which produces: lifecycle-bundleB state=INSTALLED required=ClassLoader So you can see the bundle state is inconsistent with the deployment unit state. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/534854#534854] Start a new discussion in JBoss Microcontainer Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]