Hi, Am 18.04.2008 um 11:08 schrieb Felix Meschberger:
Hi, Am Freitag, den 18.04.2008, 11:02 +0200 schrieb Alexander Saar:I like the proposal very much, as it would support my needs during development. But in future 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 (guess that's what Philipp wanted to mention). For that purposes it would be nice if one could embed the update procedure directly into the new (updated) bundle. Maybe by adding an update handler: <Sling-InitialContent> /content;update:=org.example.MyUpdateHandler </Sling-InitialContent> But we can save that for future releases, I guess. Just wanted to add my 2 cents.Sounds promising, in fact. How about creating a JIRA issue
Yep, of course. I added SLING-388 for that.
and even proposing an API for such a handler ? Thanks.
I currently have no real idea how such an interface should look like. The idea of having an update handler inside a bundle just came to my mind recently after a discussion with Carsten. But I will continue thinking about it and maybe do some tests if I have the time. As already said, I think we could add this in future releases as well.
Regards, Alex
