[jira] [Commented] (FELIX-5248) SCR does not reactivate a failed component after a configuration update

["David Jencks (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FELIX-5248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327785#comment-15327785 ] 

David Jencks commented on FELIX-5248:
-------------------------------------

I added a test that while simpler than your situation I thought would include the important parts, and currently it appears to pass.  Could you see if your original case now works properly as well, and if not see if you can figure out what is missing in my test?

> 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
>            Priority: Blocker
>
> 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.4#6332)