On 11/30/10 1:37 PM, David M. Lloyd wrote:
Comments inline.
>
> So if the OSGi service registry is the standard view of the MSC service
> registry, It should readily be available whenever you want to publish a
> service in a standard way.
>
> From my perspective #2 would be a bad choice for the same reason that
> you want to keep the MSC service registry generic (i.e. it does not know
> about any specific service)
#2 doesn't mean that the OSGi service registry has any special knowledge
of the service - it just means that in addition to setting up the OSGi
service registry, the subsystem (not the registry itself) also populates
it with known services.
Right, but the subsystem would also have to have at least a bunch of
optional module deps. If they are optional then you would have to have
some kind of reflection discovery stuff.
--
Jason T. Greene
JBoss, a division of Red Hat