Mailing-List: contact celix-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: celix-dev@incubator.apache.org
Date: Tue, 8 Jul 2014 06:29:34 +0000 (UTC)
From: "Bjoern Petri (JIRA)" <jira@apache.org>
To: celix-commits@incubator.apache.org
Message-ID: <JIRA.12719169.1402307312303.17779.1404800974858@arcas>
In-Reply-To: <JIRA.12719169.1402307312303@arcas>
References: <JIRA.12719169.1402307312303@arcas>
Subject: [jira] [Commented] (CELIX-121) remote_service_admin_shm does not
 support same-named services
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Bjoern Petri commented on CELIX-121:
------------------------------------

As mentioned, communication between celix instances when several services of the same name should be registered does not work properly yet.

As a first approach to handle this, the RemoteServiceAdmin now creates a proxyFactory per service to be able to use one proxy bundle 
to interact with all availble services of the same type. To achieve this, the used importRegistraton was replaced through an importRegistrationFactory which 
is also tracked by a ServiceTracker once it has been created. Using this factory, the RemoteServiceAdmin can now register a proxy service per imported Service. 

Note that up to now, the committed implementation can only differ between services that contain a different framework-uuid.

> remote_service_admin_shm does not support same-named services
> -------------------------------------------------------------
>
>                 Key: CELIX-121
>                 URL: https://issues.apache.org/jira/browse/CELIX-121
>             Project: Celix
>          Issue Type: Improvement
>            Reporter: Bjoern Petri
>            Assignee: Bjoern Petri
>
> The remote_service_admin_shm uses default-keys to set up shared memory communication between an endpoint and a proxy. And although this could be overwritten by setting according configuration properties (in the exported service), this solution will not work if the same service is exported by several celix frameworks.  


--
This message was sent by Atlassian JIRA
(v6.2#6252)