[
https://issues.apache.org/jira/browse/FELIX-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993881#comment-15993881
]
Pierre De Rop commented on FELIX-5630:
--------------------------------------
I committed a candidate fix in revision 1793592, where the
AbstractDependency.stop() method is now resetting the m_available flag to
false. The FELIX5630_NullObjectTest test is now passing ok with the patch.
Jeroen, can you please turn this issue to resolved state if you are ok with the
patch.
thanks !
> 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-r9
> Reporter: Jeroen Daanen
> Assignee: Pierre De Rop
> Priority: Minor
> 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.3.15#6346)
