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

Julian Reschke edited comment on OAK-101 at 5/30/12 1:53 PM:
-------------------------------------------------------------

The current status of identifier handling is:

* the identifier of nodes that seem to be referenceable (weak node type 
check...) is the value of their {{jcr:uuid}} property

* otherwise the identifier is the OAK path

This means that identifiers of non-referenceable nodes currently are unstable 
(they change on rename/move) operations, and the {{IDENTIFIER_STABILITY}} 
repository descriptor should reflect that.

Lookup is done by inspecting the identifier value, and getting the node by OAK 
path (for identifiers that look like an absolute path), and using a OAK query 
for the {{jcr:uuid}} otherwise.


                
      was (Author: reschke):
    The current status of identifier handling is:

* the identifier of nodes that seem to be referenceable (weak node type 
check...) is the value of their {{jcr:uuid}} property

* otherwise the identifier is the OAK path

Lookup is done by inspecting the identifier value, and getting the node by OAK 
path (for identifiers that look like an absolute path), and using a OAK query 
for the {{jcr:uuid}} otherwise.
                  
> implement identifier handling (byUUID, byIdentifier, etc)
> ---------------------------------------------------------
>
>                 Key: OAK-101
>                 URL: https://issues.apache.org/jira/browse/OAK-101
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: jcr
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>


--
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

        

Reply via email to