[
https://issues.apache.org/jira/browse/SLING-7786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564936#comment-16564936
]
Carsten Ziegeler commented on SLING-7786:
-----------------------------------------
Thanks to the complex OSGi installer, updating factory configurations from old
to new is more or less working out of the box. As the ID of the install
resource changes from the old "dot" notation to the new named notation using a
tilde to separate the factory pid from the name, this result in an uninstall
for the old factory configuration and an install for the new factory
configuration - if new properties are provided. If the configuration is
provided unchanged, nothing happens and the old configuration is left as is.
This avoids an extra conversion phase which is prone to race conditions (we
tried this some time ago).
I've added a basic test to the IT tests to verify this, but this needs to
consider more scenarios for further verification
> Use R7 configuration admin supporting named factory configurations
> ------------------------------------------------------------------
>
> Key: SLING-7786
> URL: https://issues.apache.org/jira/browse/SLING-7786
> Project: Sling
> Issue Type: Improvement
> Components: Installer
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: Installer Configuration Factory 1.2.0
>
>
> R7 contains special support for factory configurations by providing a name
> (alias) which makes managed the alias in our code obsolete.
> We should switch to this new api - but we also need to handle updating an
> existing instance
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
