Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <1088640373.1211351935687.JavaMail.jira@brutus>
Date: Tue, 20 May 2008 23:38:55 -0700 (PDT)
From: "angela (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Resolved: (JCR-1614) uuid of newly added node
In-Reply-To: <1308911388.1211233435699.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JCR-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela resolved JCR-1614.
-------------------------

       Resolution: Invalid
    Fix Version/s:     (was: 1.5)

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