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

Andrei Tuicu updated SLING-8578:
--------------------------------
    Description: 
h3. Problem
Nodes that contain : character are put in content packages with the help of _ , 
for example the following path /content/cq:tags/somenode in AEM would look in 
the content package like:
/jcr_root/_cq_tags/somenode .  If the content package converter would process 
this path it would generate a the following repo:init lines
{code}
"create path (sling:Folder) /content/_cq_tags",
"create path (cq:Tag) /content/_cq_tags/somenode",
{code}

Similar, if there are rep policies under that path, the output would look as 
following:
{code}
"set ACL for my-system-user",
    "allow 
jcr:versionManagement,jcr:read,rep:write,crx:replicate,jcr:lockManagement on 
/content/_cq_tags/somenode",
{code}

This results in the wrong node structure in the AEM instance, as follows:
{code}
/content
   /cq:tags    ### <- original AEM folder
   /_cq_tags   ###<- folder created by the repoinit statements
{code}

  was:
h3. Problem
Nodes that contain : character are put in content packages with the help of _ , 
for example the following path /content/cq:tags/somenode in AEM would look in 
the content package like:
/jcr_root/_cq_tags/somenode .  If the content package converter would process 
this path it would generate a the following repo:init lines
{code}
"create path (sling:Folder) /content/_cq_tags",
"create path (cq:Tag) /content/_cq_tags/somenode",
{code}

Similar, if there are rep policies under that path, the output would look as 
following:
{code}
"set ACL for my-system-user",
    "allow 
jcr:versionManagement,jcr:read,rep:write,crx:replicate,jcr:lockManagement on 
/content/_cq_tags/somenode",
{code}

This results in the wrong node structure in the AEM instance, as follows:
{code}
/content
   /cq:tags    ### <- original AEM folder
   /_cq_tags ###<- folder created by the repoinit statements
{code}


> Nodes which contain : are not correctly processed
> -------------------------------------------------
>
>                 Key: SLING-8578
>                 URL: https://issues.apache.org/jira/browse/SLING-8578
>             Project: Sling
>          Issue Type: Bug
>          Components: Content-Package to Feature Model Converter
>            Reporter: Andrei Tuicu
>            Priority: Major
>
> h3. Problem
> Nodes that contain : character are put in content packages with the help of _ 
> , for example the following path /content/cq:tags/somenode in AEM would look 
> in the content package like:
> /jcr_root/_cq_tags/somenode .  If the content package converter would process 
> this path it would generate a the following repo:init lines
> {code}
> "create path (sling:Folder) /content/_cq_tags",
> "create path (cq:Tag) /content/_cq_tags/somenode",
> {code}
> Similar, if there are rep policies under that path, the output would look as 
> following:
> {code}
> "set ACL for my-system-user",
>     "allow 
> jcr:versionManagement,jcr:read,rep:write,crx:replicate,jcr:lockManagement on 
> /content/_cq_tags/somenode",
> {code}
> This results in the wrong node structure in the AEM instance, as follows:
> {code}
> /content
>    /cq:tags    ### <- original AEM folder
>    /_cq_tags   ###<- folder created by the repoinit statements
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to