[FELIX-5320] Dependency Manager: adapter service propagates adaptee properties *after* the init (and start) callbacks are called

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: org.apache.felix.dependencymanager-r8
• Component/s: Dependency Manager
• Assignee: Unassigned
• Reporter: Andrea Leofreddi
• Created: 05/Aug/16 15:30
• Updated: 14/Nov/16 18:39

Description

In an adapter service, created using the createAdapterService method of DependencyManager class, one would expect to find the adaptee's properties being propagated to the adapter service itself, as stated in the documentation (http://felix.apache.org/documentation/subprojects/apache-felix-dependency-manager/reference/component-adapter.html).

Instead no propagation happens, and both init and start methods won't see any propagated properties.

After investigating I've found that propagations indeed happens (via AdapterServiceImpl's propagateAdapteeProperties) only after the callbacks are called.