[
https://issues.apache.org/jira/browse/SLING-11712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711679#comment-17711679
]
Carsten Ziegeler commented on SLING-11712:
------------------------------------------
We need a new method in ResourceResolver for this; I think we have two options:
* a new rename method which takes a resource and a name and renames the
resources without moving it to a different place in the tree
* a enhanced move method which allows to move and rename
My preference would be the first option as this can most likely be implemented
by every resource provider.
> 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)
