Issue Details (XML | Word | Printable)

Key: JCR-43
Type: Bug Bug
Status: Closed Closed
Resolution: Cannot Reproduce
Priority: Major Major
Assignee: Jukka Zitting
Reporter: angela
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Jackrabbit Content Repository

Restore on node creates same-name-sibling of OPV-Version child nodes

Created: 11/Feb/05 02:36 AM   Updated: 14/Jul/09 03:47 PM
Return to search
Component/s: jackrabbit-core, versioning
Affects Version/s: 0.9, 1.0
Fix Version/s: None

Time Tracking:
Not Specified

Environment: rev. 151731

Resolution Date: 08/Jan/09 11:35 AM


 Description  « Hide
Each call of Node.restore(String, boolean) creates a new same-name-sibling of any
OPV_Version child node:

- Create a node 'a' with nodetype nt:unstructured (defining it's childnodes to
  show OPV Version behaviour)
- Create a child node 'b'
- Make 'a' versionable (add mixin mix:versionable)
- Checkin/Checkout 'a'
- Restore any version of 'a'

result:
 a new same-name-sibling 'b[1]' of b is created on each call of 'a'.restore(String, boolean).

Is this the intended behaviour? Looks strange to me....

gruss
anchela



 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Roy T. Fielding added a comment - 13/Mar/05 04:51 AM
reassign to versioning component

Jukka Zitting added a comment - 30/Jun/05 11:17 PM
Schedule for 1.0

Jukka Zitting added a comment - 08/Jan/09 11:35 AM
I can't reproduce this issue anymore on 1.6-SNAPSHOT.

Added a testcase o.a.j.core.integration.RestoreSameNameSiblingTest for this. Resolving as Cannot Reproduce.