[JCR-69] removing source parent node after session move throws on save

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: JCR API
• Assignee: Stefan Guggisberg
• Reporter: Stefan Guggisberg
• Created: 16/Mar/05 18:48
• Updated: 16/Mar/05 22:31
• Resolved: 16/Mar/05 22:31

Description

the following code fragment illustrates the problem:

/**

• create the following node tree:
• + A
• + B
• + C
• + D
  */
  Node A;
  if (root.hasNode("A")) { A = root.getNode("A"); }

  else

  { A = root.addNode("A"); }

  Node B = A.addNode("B");
  Node C = B.addNode("C");
  Node D = A.addNode("D");
  root.save();

// move C under D
session.move("/A/B/C", "/A/D/C");
// remove B
A.getNode("B").remove();
/**

• the expected resulting node tree:
• + A
• + D
• + C
  */
  A.save();

==> the last save() will throw
javax.jcr.RepositoryException: inconsistency: failed to retrieve transient state for ...