The ranking concept is fine. The problem is just that if only the lower
rank service was present when the client starts then it will stick with it.
You can already restart the client bundle to make it switch but this is
pretty inconvenient.
So we need to implement the dynamic rebinding to a higher ranked service.
In fact there is already an issue for that:
https://issues.apache.org/jira/browse/ARIES-1314
I just did not get to it till now.
Christian
On 18.01.2016 12:55, cniehues wrote:
Thanks for the info. I already know about this behavior. My intention was to
provide a customer specific service implementation with a higher rank
without changing/stopping the default implementation from an installed
feature.
Let's say there is a bundle in my product providing implementation for 5
different services. If I want to provide a custom implementation for one of
the services how should I do this without ranking?
--
View this message in context:
http://karaf.922171.n3.nabble.com/How-to-set-service-ranking-with-aries-blueprint-plugin-tp4044891p4044894.html
Sent from the Karaf - User mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
