jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1614) uuid of newly added node
Date Wed, 21 May 2008 06:34:55 GMT

    [ https://issues.apache.org/jira/browse/JCR-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598563#action_12598563
] 

angela commented on JCR-1614:
-----------------------------

the node does have a dummy uuid in the jcr:uuid property.
BUT: the node is not referenceable unless save is called (this is legal according to the spec)
and therefore Node.getUUID() must throw.

> uuid of newly added node
> ------------------------
>
>                 Key: JCR-1614
>                 URL: https://issues.apache.org/jira/browse/JCR-1614
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-jcr2spi
>            Reporter: Scott Cytacki
>             Fix For: 1.5
>
>
> I'm using jcr2spi with spi2dav.
> When I add a new child node.  And add the "mix:referenceable" mixin.  
> and I don't  "save" the node.
> Calling node.getUUID();
> causes a repository exception.
> My reading of the JCR spec section 4.9.1.1
> is that a node should at least have a dummy UUID even if it hasn't been saved yet.  
> The jcr2spi.NodeImpl.createNode method has the comment:
> // NOTE: uuid is generated while creating new state.
> But I cannot find where that is happening.
> I can submit a test case for this if that would help.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message