[SLING-388] Embed update handler into bundles for handling content updates

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: JCR Contentloader 2.0.2
• Component/s: JCR
• Assignee: Unassigned
• Reporter: Alexander Saar
• Created: 18/Apr/08 11:42
• Updated: 12/Apr/23 07:18
• Resolved: 12/Apr/23 07:18

Description

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/[e-mail]/msg04049.html