You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/02/12 03:17:12 UTC
[jira] [Resolved] (SLING-4395) Configuration Installer does not
apply configuration updates
[ https://issues.apache.org/jira/browse/SLING-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-4395.
-------------------------------------
Resolution: Won't Fix
As I think this is a setup probem and as I also implemented FELIX-4410 which reverts the default behaviour, I'll close this with won't fix
> 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)