sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Burkhard Pauli (JIRA)" <>
Subject [jira] [Commented] (SLING-8186) Moved node is deleted if @Delete parameter points to its name
Date Wed, 09 Jan 2019 11:20:00 GMT


Burkhard Pauli commented on SLING-8186:

I don't see a name collision problem in the provided example. The file resource is located
at {{/content/file}} and the delete operation is against the resource {{/content/test}}. In
the provided curl command the file should be moved from {{/content/file}} to {{/content/test/file}}.
This done with the relative path {{./test}} against the target url {{http://localhost:4502/content}}.
Maybe the example is a bit misleading by mixing relative and absolute path parameters - sorry
for that.  

Changing the order of the operation will not change the behaviour of delete operation itself.

> Moved node is deleted if @Delete parameter points to its name
> -------------------------------------------------------------
>                 Key: SLING-8186
>                 URL:
>             Project: Sling
>          Issue Type: Bug
>          Components: Servlets
>    Affects Versions: Servlets Post 2.3.26
>            Reporter: Burkhard Pauli
>            Assignee: Bertrand Delacretaz
>            Priority: Major
>         Attachments: patch.diff
> If a file is moved to a new location with the @MoveFrom parameter and the request contains
the @Delete parameter at the same time, the file is dropped and never saved to the new location.
> Step to reproduce the issue:
>  # Create a node of type nt:file at the location {{/content/file}}
>  # Execute the following curl command:
>  {{curl -u admin:admin -F './test/title=Hello World' -F './test/file@MoveFrom=/content/file'
-F './test@Delete=true' [http://localhost:4502/content]}}
> Observed behaviour:
>  The file is not saved at the new location at {{/content/test/file}} and it is not available
anymore at the old location {{/content/file}}
> Expected:
>  The file is saved at the new location {{/content/test/file}} as long as other properties
are saved when the request contains the delete operation (like the title property in the example

This message was sent by Atlassian JIRA

View raw message