You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/02/28 16:29:51 UTC
[jira] Issue Comment Edited: (SLING-285) ujax post servlet should
silently replace existing move targets
[ https://issues.apache.org/jira/browse/SLING-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573317#action_12573317 ]
fmeschbe edited comment on SLING-285 at 2/28/08 7:28 AM:
------------------------------------------------------------------
Applied patch in Rev. 631993 and added testcases in Rev. 632004
Please close this issue, if it is ok for you. Thanks.
was (Author: fmeschbe):
Applied patch in Rev. 631993 and added testcases in Rev. 632004
> 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: ujax
> Reporter: Tobias Bocanegra
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
> 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.