Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 3.4.0.Final, 3.3.x-prod-ip6.0
Affects Version/s: 3.3.0.Final
Component/s: JCR
Labels:
None

Steps to Reproduce:
Hide

Create a repository, a workspace, login into this workspace

create a node in workspace, make it versionable

clone the workspace to another workspace

make 2+ changes to node in another workspace

try to merge node from cloned workspace back into original one

Expected result: node merged back correctly.
Actual result: merge fails with an exception.
Show
Create a repository, a workspace, login into this workspace create a node in workspace, make it versionable clone the workspace to another workspace make 2+ changes to node in another workspace try to merge node from cloned workspace back into original one Expected result: node merged back correctly. Actual result: merge fails with an exception.
Forum Reference:
https://community.jboss.org/message/831592#831592, https://community.jboss.org/message/820519#820519
Git Pull Request:
https://github.com/ModeShape/modeshape/pull/903
Bugzilla References:
https://bugzilla.redhat.com/show_bug.cgi?id=1000311

Description

According to JCR 2.0 spec, p. "15.9 Merge", Merge operation should work correctly on nodes with versions that are "eventual successors" (i.e. source node's version is a non-linear descendant of target node's version).

Current implementation checks versions to be only linear (i.e. direct) successors of each other.

It should be changed to check successors recursively.

Attachments

Activity

People

Assignee:: Horia Chiorean (Inactive)

Reporter:: Alexander Shelepko (Inactive)

Votes:: 1 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 2013/08/05 9:50 AM

Updated:: 2016/02/10 3:59 AM

Resolved:: 2013/08/27 6:17 AM