[jboss-osgi-dev] [JBoss OSGi Development] - Re: Unexpected dependee state changes

It's not quite ok AFAIK | If this bundle has exported any packages, the Framework must continue to make these packages available to their importing bundles until the PackageAdmin.refreshPackages method has been called or the Framework is relaunched. | Hence, from the class loading perspective bundle B should continue to work. From the service perspective, bundle B may track services that are provided by X and may unregister its own services. However, that behaviour would depend on the nature of those services. Generally, it is not ok that BundleActivator.stop() is called on bundle B (causing all of its services to get unregistered) only because one of the bundles it imports packages from gets uninstalled. I realize that this behaviour may not be natural to MC, but it is how OSGi works AFAIU. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268428#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...