aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIES-1314) Update service reference when service with higher ranking gets registered
Date Tue, 28 Apr 2015 16:10:07 GMT

    [ https://issues.apache.org/jira/browse/ARIES-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14517303#comment-14517303
] 

Guillaume Nodet commented on ARIES-1314:
----------------------------------------

I can read the following in the osgi spec, section 121.7.11
{code}
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, then the proxy must unget the reference
to the backing service (if it had gotten it) and get another service object the next time
a method on the proxy is called. If a replacement can be found immediately, the reference
listener’s bind method must be called without calling the unbind method. Other threads that
need the same service object must block until the ser- vice object has become available or
times out.
{code}

I could not find anything more.  Another way would be to try to modify the code and see if
the TCK passes.


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

Mime
View raw message