[
https://issues.apache.org/jira/browse/SLING-12300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17840127#comment-17840127
]
Paul Bjorkstrand commented on SLING-12300:
------------------------------------------
That's a good analysis, [~radu], thanks for sharing. I understand the Resource
API challenges. It makes sense to keep this as a JCR concept. I feel we can
drop that idea from contention given its significant constraints.
Regarding the other two, maybe there is a way to be able to have the best of
both worlds, by making the new {{/jcr:id/}} path available, but behind a
configuration flag ({{false}} by default). I think that would allow you to keep
the simpler implementation, but also addresses any security/exposure related
issues, since it would be an opt-in feature.
Thoughts?
> 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)
