[FELIX-4305] DependencyMananer Adapters - service properties propagation

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: dependencymanager-3.2.0
• Component/s: Dependency Manager
• Assignee: Pierre De Rop
• Reporter: Pierre De Rop
• Created: 06/Nov/13 16:36
• Updated: 21/Jul/14 22:51
• Resolved: 16/Dec/13 21:02

Description

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).