[
https://issues.apache.org/jira/browse/SLING-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573069#action_12573069
]
Felix Meschberger commented on SLING-285:
-----------------------------------------
Hmm, I think failure is ok if the target already exists, even in a scripting
environment. Otherwise you may silently overwrite data. This should not be
possible. The other problem is SNS ...
Probably the move operation must check for the target to exist and fail with a
meaningfull message.
> ujax post servlet should silently replace existing move targets
> ---------------------------------------------------------------
>
> Key: SLING-285
> URL: https://issues.apache.org/jira/browse/SLING-285
> Project: Sling
> Issue Type: Bug
> Components: microsling
> Reporter: Tobias Bocanegra
> Attachments: ujax_move_fix.r631699.patch
>
>
> currently moving a node to a new target fails (or worse: creates SNS) if the
> target node already exists. for convenient scripting and easier client
> implementation i suggest that the 'move' checks for existing targets and then
> removes them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
