[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] ConfigurationAdmin, declarative services and property propagation.

The point I was missing is that a DS component is deactivated and the (re)activated whenever ConfigurationAdmin dispatches an update event for that component. Therefore, up-to-date config properties are always accessible via ComponentContext.getProperties() when the component is activated. There is no need for the ManagedService.updated(..) callback for a DS. Thank you all for pointing me in the right direction.

Cheers,
Cameron.

BJ Hargrave wrote:
You do not need to do anything! :-)

SCR (declarative service runtime) will merge the properties from ConfigurationAdmin into the component properties (see 112.6). When the component is registered as a service, the component properties will be used as the service properties.

BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance
hargrave@xxxxxxxxxx
Office: +1 407 849 9117 Mobile: +1 386 848 3788



Cameron Ross <cross@xxxxxxxxxxxxxxxx> Sent by: equinox-dev-bounces@xxxxxxxxxxx
06/28/2006 11:21 AM
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>



To equinox-dev@xxxxxxxxxxx cc

Subject
[equinox-dev] ConfigurationAdmin, declarative services and property propagation.







Hi,

I have a declarative service that is also a ManagedService via the new ConfigurationAdmin found in the equinox incubator. The implementation seems to work fine. However, it is not clear to me how to implement property propagation, as defined on page 70-432 of the OSGi Service Platform Service Compendium (R4), for a declarative service. The spec recommends that properties updated through the ConfigurationAdmin service should be propagated to the managed service registration using ServiceRegistration.setProperties(...) . Declarative services encapsulate service registration, so how should properties be propagated?

Cameron.
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev


_______________________________________________ equinox-dev mailing list equinox-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/equinox-dev