Felix Meschberger wrote:
Taking this to the list ...
Thanks :)
Am Mittwoch, den 16.04.2008, 01:22 -0700 schrieb Carsten Ziegeler (JIRA):
[ https://issues.apache.org/jira/browse/SLING-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589463#action_12589463 ]
Carsten Ziegeler commented on SLING-311:
----------------------------------------
I'm not sure if we can use the mark for overwriting/handling the update case -
if I start a bundle, the mark will be added. If I now update the bundle,
the mark is still there. Or do you want to remove the mark on bundle stop?
If the user touched the content in the meantime and for instance added child
nodes etc., then maybe the approach described might work and seems to be good
enough.
So the content loader should try to overwrite existing nodes and properties ?
Yes. The only problem might be that a user has changed a property and
this gets then overwritten by an update. But I think this is an expected
behaviour
OTOH: The marker is used to prevent reloading of the content. Now, you would
like to have content overwrite.
Yes :)
Of course we could do as such:
* Marker existing and bundle install: Don't do nothing with the content
* Marker missing and bundle install: Load the content (overwriting if needed)
* Marker missing and system startup: Load the content (overwriting if needed)
* Marker existing and bundle update: Load the content (overwriting if needed)
* Marker missing and bundle update: Load the content (overwriting if needed)
In other words, content is loaded (create or replace) if either the
marker is missing or the bundle is being updated. If the marker exists
when the bundle is started, no content loading takes place.
Right ?
Yepp. I think this sums it up nicely.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
