The practice applies to both. The goal is that the configuring entity will augment the service properties of the configured service. BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [EMAIL PROTECTED] Office: +1 386 848 1781 Mobile: +1 386 848 3788
----- Original Message ----- From: "Steven E. Harris" [EMAIL PROTECTED] Sent: 03/05/2007 10:14 AM To: [email protected] Subject: [osgi-dev] Configuration Property propagation by ManagedServiceFactory I submitted a bug report against the iPOJO project related to propagation of Configuration Properties as Service Properties: iPOJO should automatically propagate configuration properties as service properties, per CM spec. https://issues.apache.org/jira/browse/FELIX-222 The discussion that's unfolding there is not really specific to iPOJO, so I thought it might be more appropriate to discuss the CM specification here. Does Section 104.4.3 (Property Propagation) of the CM specification apply to both ManagedService and ManagedServiceFactory, or just the former per the literal text? It's a little ambiguous because the specification says "Managed Service" with a space in between the words, so it's not necessarily referring to the actual type ManagedService. However, the subsequent reference to the single-argument updated(Dictionary) method does tie it only to ManagedService. -- Steven E. Harris _______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev _______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev
