[
https://issues.apache.org/jira/browse/OAK-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436776#comment-13436776
]
Julian Reschke commented on OAK-23:
-----------------------------------
The notes in the source with respect to this ticket imply that identifier paths
should be handled in the path mapper. However, that would imply that the path
mapper can do identifier resolution -- is this really a good idea?
> Deal with non-standard JCR path passed to the API calls
> -------------------------------------------------------
>
> Key: OAK-23
> URL: https://issues.apache.org/jira/browse/OAK-23
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Reporter: angela
>
> this issue corresponds to OAK-21 for path.
> in addition to dealing with expanded names, paths can also be 'identifier'
> paths.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
