You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2015/11/12 12:29:15 UTC
[jira] [Closed] (SLING-3697) Incorrect handling of deeply nested
aggregates
[ https://issues.apache.org/jira/browse/SLING-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Egli closed SLING-3697.
------------------------------
> Incorrect handling of deeply nested aggregates
> ----------------------------------------------
>
> Key: SLING-3697
> URL: https://issues.apache.org/jira/browse/SLING-3697
> 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.0
>
>
> With SLING-3656 we now have improved handling of structures serialized under nt:file/nt:resource nodes. For such derived nodes, Vault uses a concept called leaf aggregates, tied to a main aggregate.
> It has become apparent that our handling of leaf aggregates is insufficient, for two reasons:
> * when looking for a leaf aggregate, we don't descend into nested leaf aggregates
> * when calculating the filesystem path of an aggregate which is built from a leaf, we always assume that it has a single parent
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)