[
https://issues.apache.org/jira/browse/FELIX-5320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Leofreddi updated FELIX-5320:
------------------------------------
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 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 the 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.
> Dependency Manager: adapter service propagates adaptee properties *after* the
> init (and start) callbacks are called
> -------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-5320
> URL: https://issues.apache.org/jira/browse/FELIX-5320
> Project: Felix
> Issue Type: Bug
> Components: Dependency Manager
> Affects Versions: org.apache.felix.dependencymanager-r8
> Reporter: Andrea Leofreddi
>
> 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 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 the 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
