anonymous wrote : | No, that is / should be the right behavior, as you don't wanna have broken service stuck in some middle state. | It is legal to have a temporary error in the BundleActivator, for example because of an invalid service lookup. The same call might succeed at some later time. anonymous wrote : | Bundle::start should only be called after we're past CLASSLOADER stage. | At least in automated mode. If the user wants to do this before, it's his choice and potential fault. | There is explicit control over the transition from INSTALLED to RESOLVED via PackageAdmin. Also, a bundle that provides an export package transitions to RESOLVED when the importing bundle gets started. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4265786#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...