[ https://issues.apache.org/jira/browse/SLING-12300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839116#comment-17839116 ]
Paul Bjorkstrand commented on SLING-12300: ------------------------------------------ I'm leaning towards [~joerghoh]'s opinion as well. To me, this seems better served by a new method like {{ResourceResolver#getResoureById(String jcrId);}} Having this functionality in {{getResource(..)}} method seems to be a possible source for confusion. If I were to add in something that provides resources under the path {{/jcr:id/*}}, it almost seems like it should be from a provider that services that path. That may also bring into it more problems, because I don't know if it is semantically correct for a resource provider under a given path to provide resources for another path. Is there a reason why this can't be a new method? > Provide a way to retrieve a JCR backed resource by its node identifier > ---------------------------------------------------------------------- > > Key: SLING-12300 > URL: https://issues.apache.org/jira/browse/SLING-12300 > Project: Sling > Issue Type: New Feature > Components: JCR > Reporter: Radu Cotescu > Assignee: Radu Cotescu > Priority: Major > Fix For: JCR Resource 3.3.0 > > > Since all {{javax.jcr.Nodes}} have an identifier [0], a useful feature would > be {{Resource}} retrieval by node id, which could be its {{jcr:uuid}} > property for referenceable nodes or the path. In systems that would like to > use UUID addressing, this would reduce the need for executing JCR queries for > resource retrieval and would avoid double-reads via the JCR and then Sling > API to obtain the resource. > In order to provide a unified behaviour, paths starting with the {{/jcr:id/}} > prefix should use the resource retrieval by node identifier. > [0] - > https://javadoc.io/static/javax.jcr/jcr/2.0/javax/jcr/Node.html#getIdentifier() -- This message was sent by Atlassian Jira (v8.20.10#820010)