You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Anne-Catherine Courouppe (JIRA)" <ji...@apache.org> on 2017/04/10 16:48:41 UTC
[jira] [Commented] (ARIES-1314) Update service reference when
service with higher ranking gets registered
[ https://issues.apache.org/jira/browse/ARIES-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963156#comment-15963156 ]
Anne-Catherine Courouppe commented on ARIES-1314:
-------------------------------------------------
Hi,
What the status of this ticket? Any idea when it could be fixed?
> Update service reference when service with higher ranking gets registered
> -------------------------------------------------------------------------
>
> Key: ARIES-1314
> URL: https://issues.apache.org/jira/browse/ARIES-1314
> Project: Aries
> Issue Type: Improvement
> Components: Blueprint
> Reporter: Jochen Kraushaar
> Assignee: Christian Schneider
>
> Consider the following scenario:
> Bundle X uses the service defined by API Bundle A.
> Bundle A1 implements A and has a service ranking of 1.
> Bundle A2 implements A and has a service ranking of 10.
> The bundles get started in the following order: A, A1, X, A2
> In the current implementation X will use A1 till e.g. A1 gets stopped and started again - according to [~chris@die-schneider.net] in this post: http://karaf.922171.n3.nabble.com/Karaf-3-0-1-does-not-consider-service-ranking-set-by-Blueprint-tp4039991p4040041.html
> I propose that X switches from A1 to A2 when A2 gets registered as A2 has a higher service ranking.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)