[
https://issues.apache.org/jira/browse/SLING-11712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17955669#comment-17955669
]
Konrad Windszus commented on SLING-11712:
-----------------------------------------
The Sling POST API has rename support built in via parameter
{{:operation=move}} and {{:dest}}:
https://sling.apache.org/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html#moving-content.
That is more in line with the latter option (an enhanced move method), however
we must not change the semantics of the existing move method.
What about {{Resource moveAndRename(String srcAbsPath, String destParentPath,
String newName)}}. All parameters must be non null. That allows to speed up
operations where both move and rename should happen!
As the main resource provider is still the JCR one which allows to do move and
rename in one operation for me that would be the most reasonable method
signature.
> Enhance CRUD API to support re-name ability as part of Move method
> ------------------------------------------------------------------
>
> Key: SLING-11712
> URL: https://issues.apache.org/jira/browse/SLING-11712
> Project: Sling
> Issue Type: Improvement
> Components: API, JCR, ResourceResolver
> Reporter: Mahidhar Chaluvadi
> Priority: Minor
>
> Natively JCR API supports renaming nodes as part of the move operation.
> However when we want to completely use ResourceResolverAPI for all CRUD
> operations, as of now we see this feature is missing. Its understood that
> this capability is purely dependent on resource provide similar to the
> limitations we have for any CRUD operation we have today. Integrating this
> capability will remove the dependency on JCR APIs when the goal is to limit
> code to just use ResourceResolver API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
