[
https://issues.apache.org/jira/browse/SLING-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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.
