[dna-issues] [JBoss JIRA] Resolved: (DNA-542) jcr:uuid Property in dna:lock Custom Type Needs To Be Renamed

[Brian Carothers (JIRA)]

     [ https://jira.jboss.org/jira/browse/DNA-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers resolved DNA-542.
---------------------------------

    Resolution: Done


I accidentally committed the fix for this when I committed the fix for DNA-518.  The old jcr:uuid and dna:lockedNode properties on the dna:lock node type were combined into a dna:lockedUuid property.  This "frees up" the jcr:uuid property so that nodes can have the dna:lock primary type and the mix:referenceable mixin type if this becomes useful in the future.

> jcr:uuid Property in dna:lock Custom Type Needs To Be Renamed
> -------------------------------------------------------------
>
>                 Key: DNA-542
>                 URL: https://jira.jboss.org/jira/browse/DNA-542
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Critical
>             Fix For: 0.7
>
>
> The dna:lock custom node type (used to store information about an active lock) reuses the jcr:uuid and jcr:lockOwner properties.  However, using the jcr:uuid property in this manner means that the dna:lock node type can never be made referenceable later.  It also violates an assumption in the JpaConnector that a node's jcr:uuid refers to the UUID for that node and not some other node.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira