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

ASF GitHub Bot commented on FELIX-5892:
---------------------------------------

GitHub user timothyjward opened a pull request:

    https://github.com/apache/felix/pull/147

    [FELIX-5892] Repeated calls to getFactoryConfiguration return differe…

    …nt backing instances
    
    Signed-off-by: Tim Ward <timothyjw...@apache.org>

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/timothyjward/felix config-cache

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/felix/pull/147.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #147
    
----
commit 8c1932171b8ecb88223430928433ffe9bcaf87c5
Author: Tim Ward <timothyjward@...>
Date:   2018-07-27T14:32:04Z

    [FELIX-5892] Repeated calls to getFactoryConfiguration return different 
backing instances
    
    Signed-off-by: Tim Ward <timothyjw...@apache.org>

----


> Repeated calls to getFactoryConfiguration return different configuration 
> instances
> ----------------------------------------------------------------------------------
>
>                 Key: FELIX-5892
>                 URL: https://issues.apache.org/jira/browse/FELIX-5892
>             Project: Felix
>          Issue Type: Bug
>          Components: Configuration Admin
>    Affects Versions: configadmin-1.9.2
>            Reporter: Timothy Ward
>            Priority: Blocker
>
> When using the new getFactoryConfiguration methods the Configuration Admin 
> implementation does not store a newly created configuration in its local 
> cache. This results in a new configuration object being created each time 
> which means that the revision field is reset to 1. Any updates made to the 
> newly acquired configuration are thus not delivered to ManagedServiceFactory 
> instances because they are deemed to be "too old", at least until the 
> revision count of the new configuration overtakes the old one.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to