You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2009/12/11 13:14:18 UTC

[jira] Resolved: (SLING-694) Initial Content does not load initial content from a file

     [ https://issues.apache.org/jira/browse/SLING-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-694.
------------------------------------

       Resolution: Fixed
    Fix Version/s: JCR Contentloader 2.0.6

Added support for a file in revision: 889584

> 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
>    Affects Versions: JCR Contentloader 2.0.4
>            Reporter: Mike Pfaff
>            Assignee: Carsten Ziegeler
>             Fix For: JCR Contentloader 2.0.6
>
>
> 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.