You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Pierre De Rop (JIRA)" <ji...@apache.org> on 2015/05/21 20:28:17 UTC

[jira] [Deleted] (FELIX-4879) ConfigurationDependency should always "need instance".

     [ https://issues.apache.org/jira/browse/FELIX-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre De Rop deleted FELIX-4879:
---------------------------------


> ConfigurationDependency should always "need instance".
> ------------------------------------------------------
>
>                 Key: FELIX-4879
>                 URL: https://issues.apache.org/jira/browse/FELIX-4879
>             Project: Felix
>          Issue Type: Improvement
>            Reporter: Pierre De Rop
>            Assignee: Pierre De Rop
>            Priority: Minor
>
> Currently, the ConfigurationDependency only specifies that it "needs an instance" if there is no callback instance. But if there is a callback instance, then the "needsInstance" method returns false (because we have the callback instance already).
> So, from one side, it makes sense to not require a component instance if there is a callback instance configured (since we have the callback instance, we don't need the component instance).
> However, the callback instance is then not able to get access to the component instances while being invoked (the first time), using the Component object.
> So, the ConfigurationDependency should always have a "needsInstance" method returning true (always), even if there is a callback instance configured for the Configuration Dependency.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)