jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OAK-222) Missing path convertion in oak-jcr
Date Mon, 13 Aug 2012 09:13:37 GMT

     [ https://issues.apache.org/jira/browse/OAK-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

angela resolved OAK-222.

    Resolution: Duplicate

yet another duplicate issue creation due to unresponsive jira.
same as OAK-223
> Missing path convertion in oak-jcr
> ----------------------------------
>                 Key: OAK-222
>                 URL: https://issues.apache.org/jira/browse/OAK-222
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>            Reporter: angela
> i have the impression we discussed this ages ago.... looking at the current
> state of oak-jcr i get the impression that we still don't have consist
> usage of the proper path/name format in the various methods.
> from my understanding all paths/names passed to a oak-api call must be
> converted to oak-path and back to jcr-path before being exposed on the jcr-api.
> 2 examples without having a closer look at every single method:
> - SessionDelegate#getNode
> - SessionDelegate#getNodeByIdentifier

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


View raw message