[
https://issues.apache.org/jira/browse/SLING-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639216#action_12639216
]
Mike Pfaff commented on SLING-694:
----------------------------------
I tried it with your suggestion and it seems to work, thanks for the hint! :)
My problem is now solved with this workaround, but i still believe that the
content loader should support input from files too, not only from folders.
This feature is even mentioned in the documentation:
http://incubator.apache.org/sling/site/content-loading.html where the table
with the "Entry Type" and "Installation method" columns says that "Entry
Type"="File" should be supported.
> 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.
