Seems to be an issue of the Aries Blueprint implementation. To me it seems
that the reference to the service (A1 or A2) is set when the component (X)
is created. It only takes those services into account which exist at that
moment. If later on another service with a higher ranking is added, the
Hi,
did you think about upgrading to a newer release of Karaf, cause I think
this issue might have been fixed with a newer version of Aries.
regards, Achim
2015-04-28 16:13 GMT+02:00 jkraushaar jochen.kraush...@doubleslash.de:
Seems to be an issue of the Aries Blueprint implementation. To me
Hi Achim,
I checked the release notes of Karaf. According to them, Aries Blueprint was
updated in 3.0.3 to 1.4.2. I would really like to update to this version.
Unfortunately some of our legacy libraries are incompatible with the updates
of the JPA libraries in 3.0.3. :-(
Regards
Jochen
--
Blueprint will stay with the service it selected until this service goes
away. So for example if you would stop A1 and start it again then
blueprint would switch.
This is obviously not what people expect when the ranking is used. So I
would consider this to be either a bug or a good enhancement
What I wanted to express is that users naively will expect that
blueprint will select the service with the highest ranking. Of course
when reading the spec they will probably guess that service damping
might influence this.
Do you know if we are free to change the current behaviour or if the
I can read the following in the osgi spec, section 121.7.11
The backing service for a reference proxy must not be gotten from the
OSGi service registry until an actual service object is needed, that
is, when an actual method is called on the proxy. If the backing
service becomes unregistered,
It may not be what you expect, but thinking it is what no one expects seems a
bit extreme to me. DS has the concept of greedy and reluctant references so
you can specify which behavior you want.
david jencks
On Apr 28, 2015, at 10:26 AM, Christian Schneider ch...@die-schneider.net
wrote:
Hi Christian,
I opened an issue, thanks for your help:
https://issues.apache.org/jira/browse/ARIES-1314
Regards
Jochen
--
View this message in context:
http://karaf.922171.n3.nabble.com/Karaf-3-0-1-does-not-consider-service-ranking-set-by-Blueprint-tp4039991p4040043.html
Sent from the Karaf
Hi there,
we are using Karaf 3.0.1. I want to deploy two bundles providing the same
service with different service rankings. The rankings are set using
Blueprint.
I have the following scenario:
Bundle X uses the service defined by API Bundle A.
Bundle A1 implements A and has a service ranking
