You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2016/05/23 16:46:12 UTC
[jira] [Updated] (SLING-5744) OSGi Installer does not activate the
right config after a more prioritized config gets deleted
[ https://issues.apache.org/jira/browse/SLING-5744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated SLING-5744:
-----------------------------------
Summary: OSGi Installer does not activate the right config after a more prioritized config gets deleted (was: OSGi Installer)
> OSGi Installer does not activate the right config after a more prioritized config gets deleted
> ----------------------------------------------------------------------------------------------
>
> Key: SLING-5744
> URL: https://issues.apache.org/jira/browse/SLING-5744
> Project: Sling
> Issue Type: Bug
> Components: oving an OSGi config with more runmodes does not lead to the other config being applied.
> Affects Versions: Installer Core 3.6.4, JCR Installer 3.1.16
> Reporter: Konrad Windszus
>
> I have the following content in my repository
> {code}
> 1. /apps/configuration/config.<matchingrunmode1>/<myservice.pid>
> 2. /apps/configuration/config.<matchingrunmode1>.<matchingrunmode2/<myservice.pid>
> {code}
> After having that the configuration 2. is correctly active. Now at the same time configuration in node 1 is updated and configuration in 2. is completely removed (i.e. the node apps/configuration/config.<matchingrunmode1>.<matchingrunmode2/<myservice.pid> vanishes.
> The JcrInstaller is not correctly switching to the newly active configuration 2. but rather 1. stays active.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)