[
https://issues.apache.org/jira/browse/FELIX-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved FELIX-1832.
--------------------------------------
Resolution: Fixed
Fixed as described in the summary in Rev. 831390.
> ServiceFactory must not be deactivated if the instances fails to be created
> ---------------------------------------------------------------------------
>
> Key: FELIX-1832
> URL: https://issues.apache.org/jira/browse/FELIX-1832
> 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
>
>
> The AbstractComponentManager.Registered state (Satisfied state for delayed
> and service factory components) class tries to deactivate the component if
> the component instance cannot be created and setup. Part of this deactivation
> is actually unregistration of the service factory service.
> This may fail if the getService method is called as part of a chain of
> service activations, one of which is actually trying to get the service
> instance from the factory. It is not allowed to unregister this exact service
> in this situation.
> So, instead of deactivating the component, the component instance is just
> deleted and the component remains in the registered state.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
