felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre De Rop (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FELIX-4305) DependencyMananer Adapters - service properties propagation
Date Wed, 06 Nov 2013 16:37:19 GMT
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)

Mime
View raw message