[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] ConfigurationAdmin, declarative services and property propagation.
- From: "Neil Bartlett" <neil@xxxxxxxxxxxxxx>
- Date: Wed, 28 Jun 2006 16:33:53 +0100
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=sXVmtgT7zRy9JWJOXx4IGRHpm6uMoHFyXnt0zQ6czx2B1ymEDWqcBbepMEex2/tFQTxRGyKX4VV2DkZGPG4NYwur3symblR2mcQ0RCgJWK9PBzTZ4gr6sAhLrriCIUhtDgS8eMf60ACVisUymWouh9F1RoFTjmW3twzK0y54c20=
I don't think you should combine ConfigAdmin with DS in this way.
Instead of implementing ManagedService, your component should simply
retrieve the properties it needs using the
As stated in section 112.6 of the Compendium, DS should use
ConfigAdmin to retrieve a Configuration object that has a PID equal to
the name of the component.
On 6/28/06, Cameron Ross <cross@xxxxxxxxxxxxxxxx> wrote:
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?
equinox-dev mailing list
Senior Technical Consultant, Integility Ltd
Tel: +44 (0) 20 7043 8328
Fax: +44 (0) 20 7043 8329
LinkedIn Profile: https://www.linkedin.com/in/neilbartlett