Konrad Windszus created SLING-11001:
---------------------------------------
Summary: Target node path calculation broken in case the (source)
path points to a file
Key: SLING-11001
URL: https://issues.apache.org/jira/browse/SLING-11001
Project: Sling
Issue Type: Bug
Affects Versions: JCR ContentLoader 2.4.2
Reporter: Konrad Windszus
Assignee: Konrad Windszus
Fix For: JCR ContentLoader 2.5.0
In the context of SLING-10987 it turned out that a Sling-Initial-Content header
with the following value
{code}
SLING-INF/content/htl/repl.json;overwrite:=true;path:=/content/htl,
{code}
deserializes the content of repl.json below node {{/content/htl/repl/repl}}
instead of {{/content/htl/repl}}.
The repl.json looks like this in that case
{code}
{
"jcr:primaryType" : "nt:unstructured",
"sling:resourceType":"repl/components/repl",
"jcr:title": "HTL REPL"
}
{code}
Altought the documentation at
https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html#initial-content-loading
doesn't mention files as entry paths this behaviour seems counterintuitive and
also together with directive {{overwrite}} prevents the update of just a single
node.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
