-
Bug
-
Resolution: Fixed
-
Major
-
5.2
-
None
When calling session.move() for a node and moving it into its current parent, Jackrabbit throws an exception (due to same-name sibling checks). We should simply do that check ourselves and ignore the move operation. This affects especially methods like moveNodeBefore/After, since they're used to re-order nodes in the tree, by move action/dialog etc.
Acceptance criteria
- is related to
-
MGNLUI-2901 Consolidate MoveAction (w/ dialog) and drag-drop code
- Closed