You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2009/07/28 16:24:14 UTC
[jira] Resolved: (FELIX-1416) Wrong factory configuration behaviour
[ https://issues.apache.org/jira/browse/FELIX-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved FELIX-1416.
--------------------------------------
Resolution: Fixed
This fixes this issue.
> Wrong factory configuration behaviour
> -------------------------------------
>
> Key: FELIX-1416
> URL: https://issues.apache.org/jira/browse/FELIX-1416
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR), Specification compliance
> Affects Versions: scr-1.0.8
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: scr-1.2.0
>
>
> 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).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.