[FELIX-1416] Wrong factory configuration behaviour

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: scr-1.0.8
• Fix Version/s: scr-1.2.0
• Component/s: Declarative Services (SCR), Specification compliance
• Assignee: Felix Meschberger
• Reporter: Felix Meschberger
• Created: 28/Jul/09 13:41
• Updated: 30/Jul/10 11:57
• Resolved: 28/Jul/09 14:23

Description

Currently factory configurations are applied to component factories, such that each factory configuration instance creates a componnent
instances of a component factory. Reversly deleting a factory configuration also deletes component instances. This is not how it is specified.

Correct is, that

(1) Component Factories can only be configured with singleton configurations applying
the configuration to all instances created with newInstance
(2) Factory configurations are applied to non-component-factory components and
cause multiple component instances to be created.

To accomodate for this, the handling of components has to be redesigned: A component descriptor now causes the creation of a ComponentHolder. Depending on configuration availability a ComponentHolder will hold a single component (no configuration or singleton configuration) or multiple components (factory configuration).

Issue Links

• is required by: SLING-408 Repository service not registered when using Equinox Declarative Services
• relates to: FELIX-924 No component instance if no Configuration