[jira] Commented: (SLING-311) Record loaded content to not reload inadvertedly.
[ https://issues.apache.org/jira/browse/SLING-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589451#action_12589451 ] Carsten Ziegeler commented on SLING-311: It would be great, if the content would be overwritten if I update a bundle. This would make the development much easier. Record loaded content to not reload inadvertedly. - Key: SLING-311 URL: https://issues.apache.org/jira/browse/SLING-311 Project: Sling Issue Type: Improvement Components: Resource Reporter: Felix Meschberger Fix For: 2.0.0 Currently, the content loader always reloads content indicated as initial content from the bundles if the repository does not contain the respective content. Sometimes it may be desirable to remove the content from the repository and not get the content reloaded on bundle (or system) restart. To prevent such content reload, the content loader should take note of loaded content and not try to reload content, which is marked as loaded, regardless of whether the actual content (still) exists or not. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-311) Record loaded content to not reload inadvertedly.
[ https://issues.apache.org/jira/browse/SLING-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589456#action_12589456 ] Felix Meschberger commented on SLING-311: - I think this mark can also be used for this overwriting: If the mark is missing, content is replaced. There is one catch though: Consider a node at /apps/path loaded by the loader and content at /apps/path/child not loaded by the loader. I assume, /apps/path should be replaced while /apps/path/child might be left untouched. In this case, primary node types of the node to be replaced may probably not be changed. We can still change the mixin node types. In the end we may be left with invalid content as the nodes we do not replace may not be allowed anymore. But this is probably as good as we can do without much overloading the work. WDYT ? Record loaded content to not reload inadvertedly. - Key: SLING-311 URL: https://issues.apache.org/jira/browse/SLING-311 Project: Sling Issue Type: Improvement Components: Resource Reporter: Felix Meschberger Fix For: 2.0.0 Currently, the content loader always reloads content indicated as initial content from the bundles if the repository does not contain the respective content. Sometimes it may be desirable to remove the content from the repository and not get the content reloaded on bundle (or system) restart. To prevent such content reload, the content loader should take note of loaded content and not try to reload content, which is marked as loaded, regardless of whether the actual content (still) exists or not. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-311) Record loaded content to not reload inadvertedly.
[ https://issues.apache.org/jira/browse/SLING-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589457#action_12589457 ] Philipp Koch commented on SLING-311: the update functionality is very important in regards of bundle updates (where the bundle is supposed to update content) Record loaded content to not reload inadvertedly. - Key: SLING-311 URL: https://issues.apache.org/jira/browse/SLING-311 Project: Sling Issue Type: Improvement Components: Resource Reporter: Felix Meschberger Fix For: 2.0.0 Currently, the content loader always reloads content indicated as initial content from the bundles if the repository does not contain the respective content. Sometimes it may be desirable to remove the content from the repository and not get the content reloaded on bundle (or system) restart. To prevent such content reload, the content loader should take note of loaded content and not try to reload content, which is marked as loaded, regardless of whether the actual content (still) exists or not. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-311) Record loaded content to not reload inadvertedly.
[ https://issues.apache.org/jira/browse/SLING-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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. Record loaded content to not reload inadvertedly. - Key: SLING-311 URL: https://issues.apache.org/jira/browse/SLING-311 Project: Sling Issue Type: Improvement Components: Resource Reporter: Felix Meschberger Fix For: 2.0.0 Currently, the content loader always reloads content indicated as initial content from the bundles if the repository does not contain the respective content. Sometimes it may be desirable to remove the content from the repository and not get the content reloaded on bundle (or system) restart. To prevent such content reload, the content loader should take note of loaded content and not try to reload content, which is marked as loaded, regardless of whether the actual content (still) exists or not. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Content Overwrite in the Content Loader (was: [jira] Commented: (SLING-311) Record loaded content to not reload inadvertedly.)
Taking this to the list ... 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-tabpanelfocusedCommentId=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 ? This is particulary required probably for files. WDYT ? OTOH: The marker is used to prevent reloading of the content. Now, you would like to have content overwrite. 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 ? Regards Felix
[jira] Commented: (SLING-311) Record loaded content to not reload inadvertedly.
[ https://issues.apache.org/jira/browse/SLING-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12575851#action_12575851 ] Felix Meschberger commented on SLING-311: - Actually content is really loaded just before the bundle is started, so content loading is related to bundle start and not to bundle installation, thus you do not need to restart the system, restarting the bundle should suffice it. The goal of this issue is to prevent content reload on bundle start. Record loaded content to not reload inadvertedly. - Key: SLING-311 URL: https://issues.apache.org/jira/browse/SLING-311 Project: Sling Issue Type: Improvement Components: Resource Reporter: Felix Meschberger Fix For: 2.0.0 Currently, the content loader always reloads content indicated as initial content from the bundles if the repository does not contain the respective content. Sometimes it may be desirable to remove the content from the repository and not get the content reloaded on bundle (or system) restart. To prevent such content reload, the content loader should take note of loaded content and not try to reload content, which is marked as loaded, regardless of whether the actual content (still) exists or not. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-311) Record loaded content to not reload inadvertedly.
[ https://issues.apache.org/jira/browse/SLING-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12575870#action_12575870 ] Felix Meschberger commented on SLING-311: - Considering the content loaded mark is stored in the repository (this is what I intend actually), content will be reloaded when you remove the repository. Record loaded content to not reload inadvertedly. - Key: SLING-311 URL: https://issues.apache.org/jira/browse/SLING-311 Project: Sling Issue Type: Improvement Components: Resource Reporter: Felix Meschberger Fix For: 2.0.0 Currently, the content loader always reloads content indicated as initial content from the bundles if the repository does not contain the respective content. Sometimes it may be desirable to remove the content from the repository and not get the content reloaded on bundle (or system) restart. To prevent such content reload, the content loader should take note of loaded content and not try to reload content, which is marked as loaded, regardless of whether the actual content (still) exists or not. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
