jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] Closed: (JCR-17) Creating and saving a mix:versionable node creates two VersionHistory nodes
Date Thu, 10 Nov 2005 16:37:05 GMT
     [ http://issues.apache.org/jira/browse/JCR-17?page=all ]
     
Stefan Guggisberg closed JCR-17:
--------------------------------


closing resolved issue


> Creating and saving a mix:versionable node creates two VersionHistory nodes
> ---------------------------------------------------------------------------
>
>          Key: JCR-17
>          URL: http://issues.apache.org/jira/browse/JCR-17
>      Project: Jackrabbit
>         Type: Bug
>  Environment: Jackrabbit SVN version 56603
>     Reporter: Felix Meschberger
>     Assignee: Tobias Strasser

>
> Steps:
>    - Create a new mix:versionable node
>       [ This creates a new VersionHistory node below jcr:persistentVersionStore
>         and sets the new node's versionHistory property to the UUID of this
>         VersionHistory node. ]
>    - Save the session (or alternatively save the parent of the new node)
>       [ This creates a new VersionHistory node below jcr:persistentVersionStore
>         and sets the node's versionHistory property to the UUID of this
>         VersionHistory node. ]
> As you can see, you end up with two VersionHistory nodes for the same node, of which
the first VersionHistory node is never used again, because the second VersionHistory node
is used from now on.

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


Mime
View raw message