[
https://issues.apache.org/jira/browse/SLING-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-3697.
------------------------------------
Resolution: Fixed
* http://svn.apache.org/viewvc?view=revision&revision=1605439 initial fix
* http://svn.apache.org/viewvc?view=revision&revision=1605440 simplify
VaultFile lookup
* http://svn.apache.org/viewvc?view=revision&revision=1605441 downgrade a
warning to debug
> 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.2
>
>
> 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.2#6252)
