Jason sais
Are the dependencies of naming on OSGi necessary? It seems like these
services should be created by the osgi subsystem. Is the problem making
these optional?
I think its correct like this. The OSGi subsystem provides the OSGi
service registry. Subsystem Foo may choose to publish a service in that
registry which would then readily be available for installed bundles to
use. The OSGi subsystem does not need to know about Foo.
The dependency on org.jboss.as.osgi is there because Foo provides a
PASSIVE service which activates when the Framework comes up. If the
Framework was coming up eagerly a dependency on org.osgi.core would be
sufficient. You should see no performance impact due to these additional
services (i.e. only passive service registration)