[
https://issues.apache.org/jira/browse/FELIX-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved FELIX-1952.
--------------------------------------
Resolution: Fixed
Implemented a fix in Rev. 892241.
A ComponentFactory instance is now using different SATISFIED states:
* FACTORY -- This is for the ComponentFactory itself
* ACTIVE -- This is for (backwards compatible, non-standard) configuration
factory induced instances
* FACTORY_INSTANCE -- This is for instances created with
ComponentFactory.newInstance
This state is like ACTIVE (and advertises itself as active, too) but
disposes off the
component when it is being deactivated.
> Factory configured ComponentFactory instances not reconfigured when
> configuration updated
> -----------------------------------------------------------------------------------------
>
> Key: FELIX-1952
> URL: https://issues.apache.org/jira/browse/FELIX-1952
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Affects Versions: scr-1.4.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: scr-1.4.2
>
>
> As of FELIX-1942 instances created by ComponentFactory services are set up
> such that they are disposed off when being deactivated as required by the
> specification.
> This fix now breaks the backwards compatibility functionality where the
> ComponentFactory service creates component instances using factory
> configuration.
> The fix from FELIX-1942 should be adapted to only dispose off components
> created through ComponentFactory.newInstance but regularly cycle instances
> created for factory configurations.
> Note, that this behaviour is not specification compliant and thus spec
> compliant components are not susceptible to this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
