You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2008/02/27 22:17:51 UTC

[jira] Updated: (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:all-tabpanel ]

Tobias Bocanegra updated SLING-285:
-----------------------------------

    Attachment: ujax_move_fix.r631699.patch

fixes the replace.

> 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.