[
https://issues.apache.org/jira/browse/SLING-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639137#action_12639137
]
Carsten Ziegeler commented on SLING-694:
----------------------------------------
You're assuming correctly that the content loader is working on folders as the
basic input, therefore something like
CQ-INF/content/etc/designs/;overwrite:=true;path:=/etc/designs
with just xyz.json in "CQ-INF/content/etc/designs/" should do the trick I think.
> Initial Content does not load initial content from a file
> ----------------------------------------------------------
>
> Key: SLING-694
> URL: https://issues.apache.org/jira/browse/SLING-694
> Project: Sling
> Issue Type: Bug
> Components: JCR Contentloader
> Reporter: Mike Pfaff
>
> At the moment it is not possible to use the initial content feature to create
> a node based on a single JSON file.The initial content rule
> CQ-INF/content/etc/designs/xyz.json;overwrite:=true;path:=/etc/designs/xyz
> which should take the xyz.json file from the bundle and import it at
> /etc/designs/xyz does not work. In the log one can see entries which indicate
> that the content loader does not find the xyz.json file (maybe because the
> content loader thinks xyz.json is a folder name?).
> As we want to create (or overwrite, if it already exists) the
> /etc/designs/xyz node but leave all other existing content under /etc/designs
> intact, we have to use the xyz.json file and cannot define the whole
> designs-folder as initial content.
> It would be great and help us a lot if this bug was fixed for load 29.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
