[
https://issues.apache.org/jira/browse/SLING-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-388.
------------------------------------
Resolution: Won't Fix
> Embed update handler into bundles for handling content updates
> ---------------------------------------------------------------
>
> Key: SLING-388
> URL: https://issues.apache.org/jira/browse/SLING-388
> Project: Sling
> Issue Type: New Feature
> Components: JCR
> Affects Versions: JCR Contentloader 2.0.2
> Reporter: Alexander Saar
> Priority: Major
>
> As discussed on the list [1] the provision of initial content contained in
> bundles leads to the question how to handle content updates contained in new
> versions of bundles. While a simple overwrite flag may be enough for
> development, there might be more complex cases where you have to consider the
> (maybe modified) content in detail - or want to change the content for the
> new bundle version - if you update bundles on several production
> installations. For that purposes it would be nice if one could embed the
> update procedure directly into the new (updated) bundle and tell Sling which
> one shuld be used by adding an according bundle header parameter.
> <Sling-InitialContent>
> /content;update:=org.example.MyUpdateHandler
> </Sling-InitialContent>
> [1] http://www.mail-archive.com/[email protected]/msg04049.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
