[jira] [Commented] (SLING-7735) JcrInstaller: Switching a configuration from sling:OsgiConfig to the .config binary file format not properly supported

["Konrad Windszus (JIRA)" <ji...@apache.org>]

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

Konrad Windszus commented on SLING-7735:
----------------------------------------

The problem is most probably coming from this line: https://github.com/apache/sling-org-apache-sling-installer-factory-configuration/blob/ac873e4465948eff12744495d52a95e523936673/src/main/java/org/apache/sling/installer/factories/configuration/impl/ConfigInstallTask.java#L65. It prevents that configurations which are already active are installed a 2nd time. This check must be improved, so that this only is true in case the configuration source (i.e. the url) is really identical!

> JcrInstaller: Switching a configuration from sling:OsgiConfig to the .config binary file format not properly supported
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-7735
>                 URL: https://issues.apache.org/jira/browse/SLING-7735
>             Project: Sling
>          Issue Type: Bug
>          Components: Installer
>    Affects Versions: Installer Core 3.8.6, JCR Installer 3.1.22
>            Reporter: Konrad Windszus
>            Priority: Major
>
> If I have a repository which first contains
> {code}
> .../config/myPID [sling:OsgiConfig]
> {code}
> and this is being changed to 
> {code}
> .../config/myPID.config [nt:file]
> {code}
> The latter configuration is not being installed properly. It is marked as IGNORED in the OSGi installer and one has to manually remove the still bound old configuration (which initially came from the sling:OsgiConfig node).



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