You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2014/07/18 16:50:04 UTC

[jira] [Assigned] (SLING-3768) Be more resilient when .content.xml listing and filesystem disagree on child nodes

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

Robert Munteanu reassigned SLING-3768:
--------------------------------------

    Assignee: Robert Munteanu

> Be more resilient when .content.xml listing and filesystem disagree on child nodes
> ----------------------------------------------------------------------------------
>
>                 Key: SLING-3768
>                 URL: https://issues.apache.org/jira/browse/SLING-3768
>             Project: Sling
>          Issue Type: Bug
>          Components: IDE
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>             Fix For: Sling Eclipse IDE 1.0.2
>
>
> Right now the child resources of a ResourceProxy are read directly from the .content.xml aggregate if they exist, without taking the filesystem into account. The problems can appear in several ways:
> * An added child node can be spuriously deleted after the sync of its parent node if it is not listed in the .content.xml file
> * Sorting can try to reorder inexistent nodes and fail
> The list is probably incomplete, but what's important is that we augment/sanitize the resource's children based on the filesystem data.



--
This message was sent by Atlassian JIRA
(v6.2#6252)