[
https://issues.apache.org/jira/browse/FELIX-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre De Rop updated FELIX-2344:
---------------------------------
Attachment: FELIX2344_ExtraDependencyWithCallbackTest.java
Marcel,
The last commit seems to resolve every callback issues.
But, now, in my environment, I went further on and I think I came across
another issue: this time it concerns optional/autoconfig dependencies:
So, if you define an optional/autoconfig extra dependency from the init()
method, then the autoconfig field seems to not be injected with a NullObject.
I have attached to this issue a modified version of the testcase (see the "sc5"
consumer).
> DM / callback method is not invoked when an extra dependency is defined
> within an "init" component method.
> ----------------------------------------------------------------------------------------------------------
>
> Key: FELIX-2344
> URL: https://issues.apache.org/jira/browse/FELIX-2344
> Project: Felix
> Issue Type: Bug
> Components: Dependency Manager
> Reporter: Pierre De Rop
> Attachments: FELIX2344_ExtraDependencyWithCallbackTest.java,
> sample.instancebound.tgz
>
>
> This issue applies to the trunk version of dependency manager.
> So, it seems that when a component defines custom dependencies from its
> "init" method, then such extra dependencies only support auto configuration
> mode, and not callbacks.
> I have attached to this issue a sample maven project which reproduces the
> problem:
> In the sample, a "MyClient" component is defining (from its init() method) an
> extra required dependency over a "MyService" service, using a "bind"
> callback. So, the start() method is invoked, but the bind method has not been
> called.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
