[
https://issues.apache.org/jira/browse/OAK-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436789#comment-13436789
]
angela commented on OAK-23:
---------------------------
IMO that felt quite natural... if we do it else where we have to adjust all JCR
api method calls that take a path string and make sure identifier paths are
properly handled.
now that identifier handling has been refactored to a separate class i think
it should be feasible to use that in a jcr-level path mapper to properly convert
jcrPaths to oakPaths.
> 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
