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 2017/06/27 07:09:00 UTC

[jira] [Updated] (FELIX-5630) NullObject is created for a required dependency if the component is removed and added again to the dependency manager

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

Pierre De Rop updated FELIX-5630:
---------------------------------
    Fix Version/s:     (was: org.apache.felix.dependencymanager-r10)
                   org.apache.felix.dependencymanager-r11

> NullObject is created for a required dependency if the component is removed and added again to the dependency manager
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: FELIX-5630
>                 URL: https://issues.apache.org/jira/browse/FELIX-5630
>             Project: Felix
>          Issue Type: Bug
>          Components: Dependency Manager
>    Affects Versions: org.apache.felix.dependencymanager-r1
>            Reporter: Jeroen Daanen
>            Assignee: Pierre De Rop
>            Priority: Minor
>             Fix For: org.apache.felix.dependencymanager-r11
>
>         Attachments: Activator.java
>
>
> I have a component A with a required dependency to B and C. 
> I add A, B and C to the dependency manager. 
> Then I remove A and B. 
> Finally I only add A again. Now the exception "Could not create null object for class com.example.Activator$B is thrown". See the attached Activator.
> I did not expect that a NullObject is ever created for a required dependency.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)