[
https://issues.apache.org/jira/browse/SLING-7735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-7735:
-----------------------------------
Description:
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 marked as {{IGNORED}} in the OSGi installer. This
is the case, because the old configuration already had the correct data and
hence the configuration has not been updated via the ConfigurationAdmin. The
state is rather confusing though, because in fact, exactly that configuration
is installed in the system. Therefore I would propose to mark the configuration
installer resource rather with {{INSTALLED}}.
was:
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).
> 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 Configuration Factory 1.1.2
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: Installer Configuration Factory 1.2.0
>
>
> 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 marked as {{IGNORED}} in the OSGi installer. This
> is the case, because the old configuration already had the correct data and
> hence the configuration has not been updated via the ConfigurationAdmin. The
> state is rather confusing though, because in fact, exactly that configuration
> is installed in the system. Therefore I would propose to mark the
> configuration installer resource rather with {{INSTALLED}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
