[FELIX-4600] Cherrypicking of propagated properties

• Type: Wish
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: dependencymanager.annotations-3.2.0, dependencymanager.runtime-3.2.0
• Fix Version/s: org.apache.felix.dependencymanager-r1
• Component/s: Dependency Manager, Dependency Manager Annotations, Dependency Manager Runtime
• Assignee: Pierre De Rop
• Reporter: Tuomas Kiviaho
• Created: 06/Aug/14 05:35
• Updated: 19/Mar/15 06:03
• Resolved: 16/Jan/15 23:19

Description

Currently osgi.command.scope and osgi.command.function flood down from my @AdapterService because there is no propagation prevention mechanism as per @BundleAdapterService (also mentioned at FELIX-4594). This also applies @AspectService annotation.

Still with these options the propagation from adapters/aspects is currently uncontrollable compared to dependencies where - albeit cumbersome - you still can write your own logic.

My use case is with propagated adapter/aspect identity properties (such as service.pid, jmx.objectname, osgi.command.scope, osgi.command.function) that I'd rather not see automatically propagated.

There is already a setPropagate(Object, String) method in ServiceDependency. I think this mechanism could also be available for annotations alongside the propagate boolean property. (Perhaps a String propagated() default "")

I suggest that internal m_serviceProperties would be changed as map (since @Start annotation allows this already) and keys with null values would be considered non-propagable. Internal map would be converted to Dictionary each time in passes API/Impl boundary and at this point keys with null values would be dropped.

Issue Links

• relates to: FELIX-4594 Propagation from dependencies overwrites service properties