[
https://issues.apache.org/jira/browse/SLING-7786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16577878#comment-16577878
]
Carsten Ziegeler commented on SLING-7786:
-----------------------------------------
While the already implemented approach works for the cases covered by the
tests, it will get challenging getting full covered of use cases.
The basic problem is that if the OSGi installer gets a installable resource
where the digest is the same as previously, the OSGi installer does nothing
(which in general is good). However in this case it is problematic as the "id"
of the artifact changes from <factoryPid>-<name> to <factoryPid>~<name> . This
change of the id makes sense to follow the configuration admin specification
(and if we don't change it we run into other problems).
Working through all these use cases I now think that the OSGi installer should
somehow support such a scenario. Maybe by using a marker interface on the
ResourceTransformer or something along those lines. In this case, the OSGi
installer could simply pass all old resources to the configuration plugin, that
one could do the update as required and we have a clean path.
> 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)
