You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2004/11/04 17:32:32 UTC
[jira] Created: (JCR-17) Creating and saving a mix:versionable node creates two VersionHistory nodes
Creating and saving a mix:versionable node creates two VersionHistory nodes
---------------------------------------------------------------------------
Key: JCR-17
URL: http://nagoya.apache.org/jira/browse/JCR-17
Project: Jackrabbit
Type: Bug
Environment: Jackrabbit SVN version 56603
Reporter: Felix Meschberger
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://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (JCR-17) Creating and saving a mix:versionable node creates two VersionHistory nodes
Posted by "Tobias Strasser (JIRA)" <ji...@apache.org>.
[ http://nagoya.apache.org/jira/browse/JCR-17?page=history ]
Tobias Strasser resolved JCR-17:
--------------------------------
Resolution: Fixed
fixed at revision 76106
> Creating and saving a mix:versionable node creates two VersionHistory nodes
> ---------------------------------------------------------------------------
>
> Key: JCR-17
> URL: http://nagoya.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://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Assigned: (JCR-17) Creating and saving a mix:versionable node creates two VersionHistory nodes
Posted by "Tobias Strasser (JIRA)" <ji...@apache.org>.
[ http://nagoya.apache.org/jira/browse/JCR-17?page=history ]
Tobias Strasser reassigned JCR-17:
----------------------------------
Assign To: Tobias Strasser
> Creating and saving a mix:versionable node creates two VersionHistory nodes
> ---------------------------------------------------------------------------
>
> Key: JCR-17
> URL: http://nagoya.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://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (JCR-17) Creating and saving a mix:versionable node creates two VersionHistory nodes
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ 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