Hi,
JCR 2.0 defines two different formats for names/paths:
1) Qualified
2) Expanded
(https://developer.adobe.com/experience-manager/reference-materials/spec/jcr/2.0/3_Repository_Model.html#3.2.5%20Lexical%20Form%20of%20JCR%20Names)

Although the former is the default I am wondering about the latter (as this is 
potentially more stable, e.g. against session local remapping)
Is the Sling JCRResourceProvider supporting both?
Currently 
https://sling.apache.org/documentation/the-sling-engine/resources.html#jcr-based-resources
 does not state anything about this.
Is anyone aware of limitations/capabilities in this area?

Thanks,
Konrad

Reply via email to