"alesj" wrote : I'm actually wondering what's the best or proper way to
expose or use this services in MC.
| What should be the keys that we expose or match.
| "alesj" wrote :
| | * Service --> MC
| In OSGi service we expose classes and properties.
| Probably the key could look something like this:
| * org.jboss.acme.X,org.jboss.acme.Y;(a=b)
| a set of FQNs and a filter.
| Only matching services that expose all the FQNs and match the filter.
| Perhaps if there are no properties, we could directly expose service under registered
What do you mean by key?
The name of the OSGi service context should be something generated that won't change
or interfere with other names
e.g. a UID or $OSGiService + serviceID
Ideally you need an index (rather than a key) by class name to optimize the search
but we don't currently do that in the OSGi prototype.
You should already have something similar for the anonymous injection
and the install callbacks which should be more efficient than what is currently used?
The only thing that is probably missing is the security check?
View the original post :
Reply to the post :