[ https://issues.apache.org/jira/browse/SLING-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu reassigned SLING-3710: -------------------------------------- Assignee: Robert Munteanu > Incorrect handling of nt:hierarchyNode instances nested within jcr:content > nodes of other nt:hieararchyNode node > ---------------------------------------------------------------------------------------------------------------- > > Key: SLING-3710 > URL: https://issues.apache.org/jira/browse/SLING-3710 > Project: Sling > Issue Type: Bug > Components: IDE > Affects Versions: Sling Eclipse IDE 1.0.0 > Reporter: Robert Munteanu > Assignee: Robert Munteanu > Fix For: Sling Eclipse IDE 1.0.2 > > > Consider the following content structure > {code} > - mapping1 [sling:Mapping] > \- jcr:content [nt:unstructured] > \- par1 [nt:unstructured] > \- par2 [nt:unstructured] > + jcr:title = "Title" > \- folder [sling:Folder] > {code} > FileVault will try to collapse all nodes under the jcr:content child node in > the same .content.xml aggregate. However, since it encounters an nt:folder > node, it will create the filesystem hierarchy as well, leading to the > following filesystem representation: > {code} > . > └── mapping1 > ├── .content.xml > └── _jcr_content > └── par2 > └── folder > └── .content.xml > {code} > Since we encounter a plain folder at {{mapping1/_jcr_content/par2}}, we > assume it's a nt:folder node and don't look at {{mapping1/.content.xml}} to > see if its attributes are serialized there. -- This message was sent by Atlassian JIRA (v6.2#6252)