[
https://issues.apache.org/jira/browse/FELIX-5320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421341#comment-15421341
]
Andrea Leofreddi commented on FELIX-5320:
-----------------------------------------
Hello Pierre,
thanks for the answer, and sorry for my late reply. Indeed I'm trying to use
init callback because I want to add an additional dependency which is in turn
based on the adaptee's properties. Is that reasonable, or the service adapter
is not the right tool to use?
Kind regards,
Andrea
> 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 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
