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

Timothee Maret edited comment on SLING-4395 at 2/9/15 6:07 PM:
---------------------------------------------------------------

[~cziegeler] thanks for your message. We are running an internal release of 
org.apache.felix.scr
{code}
        1.6.3.R1409029
{code}

Using the latest version 1.8.2 show the same behaviour as described in this 
issue.


was (Author: marett):
[~cziegeler] thanks for your message. We are running an internal release of 
org.apache.felix.scr
{code}
        1.6.3.R1409029
{code}

> Configuration Installer does not apply configuration updates
> ------------------------------------------------------------
>
>                 Key: SLING-4395
>                 URL: https://issues.apache.org/jira/browse/SLING-4395
>             Project: Sling
>          Issue Type: Bug
>          Components: Installer
>    Affects Versions: Installer Configuration Factory 1.1.0
>            Reporter: Timothee Maret
>            Priority: Critical
>             Fix For: Installer Configuration Factory 1.1.2
>
>
> In our setup, we are running the following "relevant" bundles
> org.apache.sling.installer.factory.configuration 1.1.0
> org.apache.felix.configadmin  1.8.0
> We deploy a component com.sample.MyComponent that is configured via a nt:file 
> configuration in the repository (under 
> /apps/system/config/com.sample.MyComponent.config).
> We noticed that when modifying a property of the configuration, the component 
> will not pick up the change.
> Looking at the OSGI component console (/system/console/components/{cid}) 
> shows the old properties.
> Looking at the OSGI config manager console (/system/console/configMgr) for 
> the related component shows the "Configuration Binding" as being "?".
> This new state "?" seems to have been introduced in SLING-4263 and thus, may 
> be expected according to the bug description.
> However, it looks like although the configuration rightly set "?", this new 
> value is not correctly interpreted thus making our component running with the 
> old configuration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to