[
https://issues.apache.org/jira/browse/SLING-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068553#comment-14068553
]
Robert Munteanu commented on SLING-3768:
----------------------------------------
* http://svn.apache.org/viewvc?view=revision&revision=1612271 - cleanup - pass
less Repository instances around
* http://svn.apache.org/viewvc?view=revision&revision=1612272 - start work on a
ResourceChangeCommandFactoryTest to allow for more fine-grained tests on the
vlt commands.
* http://svn.apache.org/viewvc?view=revision&revision=1612273 - do not attempt
to change the primary node type of the root node, as that is an illegal
operation
* http://svn.apache.org/viewvc?view=revision&revision=1612275 - normalise the
resource proxy's children based on the filesystem representation
> 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)
