You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@felix.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2013/02/23 21:10:12 UTC

[jira] [Commented] (FELIX-3915) [DS] Timing hole between ComponentHolder initial config and registration

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

David Jencks commented on FELIX-3915:
-------------------------------------

I thought of a way to avoid possible double configuration on startup, rev 1449401.
                
> [DS] Timing hole between ComponentHolder initial config and registration
> ------------------------------------------------------------------------
>
>                 Key: FELIX-3915
>                 URL: https://issues.apache.org/jira/browse/FELIX-3915
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-1.8.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: scr-1.8.0
>
>
> Right now when we create a component holder we first try to configure it with any existing configurations and then register it to obtain configuration events for it's pid.  Thus there is a timing hole after the query for existing configurations and before the registration when configuration events will be dropped.
> I'm doing the initial configuration after adding the holder to the by-pid map.  Instead of missing the configuration entirely, it will be possible that the component would get configured twice.  I don't think this can cause any harm.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira