Peter Kriens <[EMAIL PROTECTED]> writes: > This is applicable for both Managed Services as well as Managed > Service Factories.
That's the part that's not so clear, as the propagation was also omitted from the ManagedServiceFactory code example in Section 104.6.5. For a future version of the specification, it would be helpful to add just a few clarifying words that address the advice to both ManagedService and ManagedServiceFactory. > So this is just a good practice recommendation. Ignoring this > section, or doing the reverse is ok. I see. For security reasons¹, it might make sense for a consuming ManagedService to swallow and not propagate certain parameters that it does understand, but it can't make judgments about parameters it doesn't know anything about. It's difficult for a framework like DS or iPOJO to automate these decisions. Does DS do any propagation by default, or does it expect that a created instance would do the propagation via ServiceReference.setProperties(Dictionary)? Footnotes: ¹ Though these properties would still be visible to others via ConfigurationAdmin.getConfiguration() or listConfigurations(). -- Steven E. Harris _______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev
