[FELIX-3377] Allow a component to update its own service properties

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: scr-1.6.0
• Fix Version/s: scr-1.6.2
• Component/s: Declarative Services (SCR)
• Assignee: Felix Meschberger
• Reporter: David Jencks
• Created: 07/Mar/12 08:19
• Updated: 20/Nov/12 10:58
• Resolved: 10/May/12 00:29

Description

If you just register a service in code, you can give the ServiceRegistration to the service and it can update its service properties to reflect what it can discover about its environment. This proposes that services registered through DS should be able to do this too, by calling an updateProperties(Dictionary) method on the ComponentContext. (Since we'd need a spec update to add the method to ComponentContext, I added a new interface that ComponentContextImpl implements).

Right now a service could get Config Admin and modify the properties there, but then (a) the update method is called even though the component itself initiated the changes and (b) the new property values are persisted which is presumably not desired.

According to the spec config admin properties override default property values specified in the component xml. I think that in order to reduce confusion, once a property has been set through config admin it should not be possible to update it through this update method. This also makes implementing this idea easy.

IIUC this idea does not make sense for component factories.

This idea was originally suggested by Erin Schnabel in OSGI bug 2250.