felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-5248) SCR does not reactivate a failed component after a configuration update
Date Tue, 03 May 2016 17:07:12 GMT

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

David Jencks commented on FELIX-5248:

Can you provide more information about the scenario you are talking about?  If not a test
case, at least some indication of how many components, any references, and the immediate setting.
 Also more information about the sequence of events you'd like to have happen.

For instance, providing the factory configuration to a component that provides a service is
going to register the service.  If the component isn't immediate, then we'll try to create
the service when someone asks for it.  If the configuration changes, someone has to ask for
it again in order for it to get created.  If you are using the lookup strategy or the event
strategy with ServiceReference, you can try again whenever you want.

> 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

This message was sent by Atlassian JIRA

View raw message