[
https://issues.apache.org/jira/browse/FELIX-5248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved FELIX-5248.
-------------------------------------
Resolution: Fixed
Assignee: David Jencks
As there has been no response for quiet some while and as David's test passes,
I consider this now as fixed.
> SCR does not reactivate a failed component after a configuration update
> -----------------------------------------------------------------------
>
> Key: FELIX-5248
> URL: https://issues.apache.org/jira/browse/FELIX-5248
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Affects Versions: scr-2.0.4
> Reporter: Timothy Ward
> Assignee: David Jencks
> Priority: Blocker
> Fix For: scr-2.0.6
>
>
> A configurable SCR component may fail to activate by throwing an exception if
> the factory configuration contains bad values. If the factory configuration
> for that component is then updated SCR should attempt to recreate and
> activate the component. Instead the component sits in the "satisfied" state
> forever, and updates to the factory configuration are ignored.
> This makes it impossible to "fix" a mistaken configuration without deleting
> and recreating it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
