[
https://issues.apache.org/jira/browse/SLING-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598240#action_12598240
]
Felix Meschberger commented on SLING-464:
-----------------------------------------
Implementing this functionality by adding a new parameter :applyTo which takes
the paths to items to apply the operation to. When using the :applyTo parameter
the operations act slightly differently than without using this parameter:
* 201/CREATED is never set: when using :applyTo with the move and copy
operations, successfull operation is always flagged with 200/OK regardless of
whether one or more items have been created during the operation.
* Missing resources in the :applyTo list are ignored: If the :applyTo parameter
contains an entry which is not the path of an existing JCR based resource, the
entry is ignored
* Destination path must be slash-terminated: When using the :applyTo parameter
with the move and copy operations, the :dest parameter must always be set to a
path with a trailing slash. Otherwise a 500/INTERNAL SERVER ERROR occurrs.
* Existing content is replaced: when using the :applyTo parameter with the move
and copy operations, any content already existing at the destination location
is replaced by items to be moved or copied. The :replace parameter is not used.
> Allow operations to apply to multiple items
> -------------------------------------------
>
> Key: SLING-464
> URL: https://issues.apache.org/jira/browse/SLING-464
> Project: Sling
> Issue Type: New Feature
> Components: Servlets Post
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> After implementing SLING-422, the SlingPostServlet can only execute one
> single operation on a single item. It shows that some times, it is required
> to actually apply an operation to muiltiple items: In some administration
> application, an operation such as moving items may be applied to multiple
> items at once. So having a way of specifying all such items at once would be
> required.
> Both use cases require multiple requests after the SLING-422 implementation.
> (This issue is a splin-off of issue (2) in SLING-458)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
