Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Date: Wed, 2 May 2012 15:34:50 +0000 (UTC)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: oak-dev@jackrabbit.apache.org
Message-ID: 
 <776782111.17433.1335972890672.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1655464624.23943.1331897738989.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (OAK-23) Deal with non-standard JCR path passed
 to the API calls
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jukka Zitting commented on OAK-23:
----------------------------------

bq. Thus our assumption that they never occur on Oak paths is wrong.

Depends on the scope of the assumption. Such a PATH value would never be a valid argument to a Root.getTree() call or be returned by a Tree.getPath() call.

As far as oak-core is concerned, such a value is just an opaque string tagged with PropertyType.PATH in a CoreValue instance, *not* an Oak path that identifies some particular node or property. Any mapping of such values should happen entirely on the oak-jcr level.

                
> 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