[
https://issues.apache.org/jira/browse/SLING-7786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578580#comment-16578580
]
Carsten Ziegeler commented on SLING-7786:
-----------------------------------------
I've now chosen a different approach, the installer now supports updating the
entity id and the alias through resource updater plugin.
This way, the configuration factory can install should an updater as a first
step, everything can be updated from old factory configs to new named factory
configs (including changing the entity id and removing the alias), once that is
done, the configuration factory registers the normal transformer/task factory
service which then can simply act on named factory configurations
This gives us a clean code and a clean upgrade on updating the bundle
> 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, Installer Core
> 3.8.14
>
>
> 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)
