[ https://issues.apache.org/jira/browse/SLING-12197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795389#comment-17795389 ]
Stefan Seifert commented on SLING-12197: ---------------------------------------- following my example from above, after deployment of [^io.wcm.handler.link-apps-1.10.2-cp2fm-converted.zip], the following folders and node types exist: * {{/apps}}: {{sling:Folder}} (already existed) * {{/apps/wcm-io}}: {{sling:Folder}} (automatically created, outside path in filter.xml) * {{/apps/wcm-io/handler}}: {{sling:Folder}} (automatically created, outside path in filter.xml) * {{/apps/wcm-io/handler/link}}: {{nt:folder}} (automatically created, toplevel path defined in filter.xml, no {{.content.xml}} exists) * all folders below {{/apps/wcm-io/handler/link}} are using {{nt:folder}} as well i do not understand why {{sling:Folder}} is used for the first two created hierarchy nodes (following the parent folder), and then it switches to {{nt:folder}} further down in the hierarchy. should not be the case according to [https://jackrabbit.apache.org/filevault/filter.html#Uncovered_ancestor_nodes]? > cpconverter: Sling-Initial-Content directories created as nt:folder instead > of sling:Folder > ------------------------------------------------------------------------------------------- > > Key: SLING-12197 > URL: https://issues.apache.org/jira/browse/SLING-12197 > Project: Sling > Issue Type: Bug > Components: Content-Package to Feature Model Converter > Affects Versions: Content-Package to Feature Model Converter 1.3.4 > Reporter: Stefan Seifert > Priority: Major > Fix For: Content-Package to Feature Model Converter 1.3.6 > > Attachments: io.wcm.handler.link-apps-1.10.2-cp2fm-converted.zip > > > the cpconverter extracts Sling-Initial-Content from OSGi bundles and creates > FileVault packages with the transformed content. > this works well, but there is one difference when the resulting content > package is installed compared when uploading the OSGi bundle with the > Sling-Initial-Content directly: > * the JCR Content Loader by defaults creates a {{sling:Folder}} node type for > each directory found in the Sling-Initial-Content (see also > [docs|https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html#initial-content-loading-1]) > * the cpconverter process creates no {{.content.xml}} file for the folders, > but only for the actual JSON files found in the process. as a result, the > folders are created as {{nt:folder}} when uploading the transformed package > * this difference becomes relevant, when a JSON file in Sling-Initial-Content > defines a primary type of {{nt:unstructured}} - it is not allowed to created > such a node directly below a {{nt:folder}} node - but it is allowed to do so > below a {{sling:Folder}} node -- This message was sent by Atlassian Jira (v8.20.10#820010)