Mailing-List: contact dev-help@aries.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aries.apache.org
Date: Tue, 28 Apr 2015 14:48:06 +0000 (UTC)
From: "Jochen Kraushaar (JIRA)" <jira@apache.org>
To: dev@aries.apache.org
Message-ID: <JIRA.12825545.1430232466000.7666.1430232486639@Atlassian.JIRA>
In-Reply-To: <JIRA.12825545.1430232466000@Atlassian.JIRA>
References: <JIRA.12825545.1430232466000@Atlassian.JIRA>
 <JIRA.12825545.1430232466975@arcas>
Subject: [jira] [Created] (ARIES-1314) Update service reference when service
 with higher ranking gets registered
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jochen Kraushaar created ARIES-1314:
---------------------------------------

             Summary: 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


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.4#6332)