[FELIX-1832] ServiceFactory must not be deactivated if the instances fails to be created

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: scr-1.2.0
• Fix Version/s: scr-1.2.0
• Component/s: Declarative Services (SCR)
• Assignee: Felix Meschberger
• Reporter: Felix Meschberger
• Created: 30/Oct/09 17:06
• Updated: 08/Dec/09 15:49
• Resolved: 30/Oct/09 17:08

Description

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.