[
https://issues.apache.org/jira/browse/SLING-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16735820#comment-16735820
]
Carsten Ziegeler commented on SLING-8186:
-----------------------------------------
I guess I'm overlooking something, but the old code:
https://github.com/apache/sling-org-apache-sling-servlets-post/blob/8982b19afcd8a2cc1aea81b93863e600f50b2ba2/src/main/java/org/apache/sling/servlets/post/impl/operations/ModifyOperation.java#L345
first checks whether a property with that name exists, if so it deletes it. If
not, it deletes the node.
Isn't that the same logic as we have now?
> Moved nt:file node disappears when @Delte parameter is used in same request
> ---------------------------------------------------------------------------
>
> Key: SLING-8186
> URL: https://issues.apache.org/jira/browse/SLING-8186
> Project: Sling
> Issue Type: Bug
> Components: Servlets
> Affects Versions: Servlets Post 2.3.26
> Reporter: Burkhard Pauli
> Priority: Major
>
> 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 above).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
