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
classes?
"alesj" wrote :
| * MC --> Service
|
This looks easier from matching pov - simply do an intersection on the contexts that type
match given FQNs (classes).
But how to mock (or even get) beans bundle?
Where this mock could be done, what about its "using bundles"?
Only count this in previous mock bundle, but ignore plain MC bean injection / usage?
"adrian(a)jboss.org" wrote :
| The proper way to do this would be to push the OSGi Filter into kernel project
| and use the MDR INSTANCE scope as the attributes.
| There would be a gotcha in that OSGi expect attributes to have case insensitive
names,
| but we would only have to enforce that for OSGi created services.
|
Or what exactly did you have in mind here?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264706#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...