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 Fri, 17 Aug 2012 15:35:37 GMT

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

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

Moving it into the mapper is attractive because we then do not need to touch anything else
(hopefully). It might be unattractive because we make something that was supposed to be simple
a bit more complex.

FWIW, the check for identifier paths is for starts-with-[ and ends-with-], right?
                
> 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