You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/01/12 13:58:35 UTC
[jira] [Closed] (SLING-4271) Provide a way to mark a resource as a
template
[ https://issues.apache.org/jira/browse/SLING-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-4271.
-----------------------------------
> Provide a way to mark a resource as a template
> ----------------------------------------------
>
> Key: SLING-4271
> URL: https://issues.apache.org/jira/browse/SLING-4271
> Project: Sling
> Issue Type: New Feature
> Components: Installer
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Installer Core 3.6.0, Installer Configuration Factory 1.1.0
>
>
> We need a way to mark a resource as a template. This can be done through a property in the dictionary:
> If this property is set (the value is ignored), this artifact acts like a template:
> If the artifact is changed into a new artifact and later this new artifact is deleted, the installer will not revert to the template. Without this property, the installer would install the original artifact again.
> For example: if a configuration is installed and then changed through configuration admin, a new artifact for the new configuration is created and managed. If now this configuration is deleted through configuration admin and the original configuration is not marked as a template, the original configuration is applied: the delete through config admin is not a remove of the configuration but a revert to the initial version.
> If the initial configuration is marked as template with this property, the removal of the changed configuration results in a real removal.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)