[
https://issues.apache.org/jira/browse/SLING-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033907#comment-13033907
]
Markus Joschko commented on SLING-2078:
---------------------------------------
There is already a parameter :replace on the operation. And only if this is
true, the node should be replaced.
However the implementation of that parameter in the parent class seems to be a
bit flaky as it is not used if a node is moved to a "/" location!
For me that seems to be a bug in its own but I don't want to modify the code as
I don't know why it is implemented the way it is and the intention of it and no
unit tests are given.
Also the code is used as parent for copy and move which makes it even more
dangerous to modify it.
> Move operation is not handling same name siblings
> -------------------------------------------------
>
> Key: SLING-2078
> URL: https://issues.apache.org/jira/browse/SLING-2078
> Project: Sling
> Issue Type: Improvement
> Components: Servlets
> Reporter: Markus Joschko
> Fix For: Servlets Post 2.1.2
>
> Attachments: snssupport.diff
>
>
> The move operation does not support same name siblings but always remove
> childnodes with the same name of the moved node.
> The attached patch checks whether the node is a sns and in this case does not
> remove the child.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
