[
https://issues.apache.org/jira/browse/FELIX-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved FELIX-1733.
--------------------------------------
Resolution: Fixed
The ConfiguredComponentHolder is generally always keeping at least one
component which may be configured. This component, though, must not be kept if
the components of the holder are all to be disposed off during disposal of the
component holder.
In Rev. 824123 the ConfiguredComponentHolder.disposeComponents(int) now sets
the single component field to null preventing the disposed(ImmediateComponent)
callback to recreate the single component.
> Disposed components are not removed from the component registry
> ---------------------------------------------------------------
>
> Key: FELIX-1733
> URL: https://issues.apache.org/jira/browse/FELIX-1733
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Affects Versions: scr-1.2.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: scr-1.2.0
>
>
> Stopping bundles disposes the bundle's components. But the components remain
> registered in the component registry.
> Listing the components later through the Web Console or the Shell Command
> results in NullPointerException because the bundle field of the components
> has been set to null.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
