jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-23) Deal with non-standard JCR path passed to the API calls
Date Mon, 14 May 2012 15:31:51 GMT

    [ https://issues.apache.org/jira/browse/OAK-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274681#comment-13274681
] 

Julian Reschke commented on OAK-23:
-----------------------------------

Applied the following WIP changes:

- SessionImpl.getItem(identifier) delegates to getNodeByIdentifier -- we may want to move
this to AbstractSession instead

- move identifier handling from *Impl to *Delegate

- sepcial-case identifier paths in PropertyImpl/ValueImpl/ValueFactoryImpl - maybe this should
happen in a special variant of the path mappers instead

(Reminder: for now a node's identifier is it's Oak path; we do not handle mix:referenceable
at all)
                
> 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

        

Mime
View raw message