Return-Path: X-Original-To: apmail-felix-dev-archive@www.apache.org Delivered-To: apmail-felix-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4032210D8D for ; Wed, 6 Nov 2013 16:37:30 +0000 (UTC) Received: (qmail 30713 invoked by uid 500); 6 Nov 2013 16:37:28 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 29479 invoked by uid 500); 6 Nov 2013 16:37:21 -0000 Mailing-List: contact dev-help@felix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@felix.apache.org Delivered-To: mailing list dev@felix.apache.org Received: (qmail 29414 invoked by uid 99); 6 Nov 2013 16:37:19 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Nov 2013 16:37:19 +0000 Date: Wed, 6 Nov 2013 16:37:19 +0000 (UTC) From: "Pierre De Rop (JIRA)" To: dev@felix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (FELIX-4305) DependencyMananer Adapters - service properties propagation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Pierre De Rop created FELIX-4305: ------------------------------------ Summary: DependencyMananer Adapters - service properties propagation Key: FELIX-4305 URL: https://issues.apache.org/jira/browse/FELIX-4305 Project: Felix Issue Type: Improvement Components: Dependency Manager Reporter: Pierre De Rop When creating an adapter service, the adapter service inherits the service properties of the adapted service (aspect, service id, service rank and object class excluded) and can have additional properties specified. For example: Service A [ objectClass=X, service.id=1, name=Piet ] A serviceAdapter on A looks like: ServiceAdapter A [ objectClass=Y, service.id=2, name=Piet, system=X] It inherits the non-identifying service properties from A (name), and can have additional properties defined (system). Now I change the service properties for Service A. After this, it looks like: Service A [ objectClass=X, service.id=1, name=Sint ] But after this change, the service properties modification is not propagated to the ServiceAdapter, which is currently unaffected: ServiceAdapter A [ objectClass=Y, service.id=2, name=Piet, system=X] It is desirable to propagate the changed properties of "A" to the "ServiceAdapter A", so it then becomes: ServiceAdapter A [ objectClass=Y, service.id=2, name=Sint, system=X] It is then the responsibility of clients depending on the service adapter to listen to service properties change events (using the ServiceDependency "change" callback). -- This message was sent by Atlassian JIRA (v6.1#6144)