- with nodes A and B, renaming A to B is not prevented, resulting in two nodes with name B, which JCR seems to be fine with (a JCR Query would show B, B[2], B[3]... though all these nodes do have name B. Somehow it's an array of Bs).
- with properties A and B, renaming A to B is not prevented, resulting in deletion of property A and overwrite of property B with A's value.
- with node A and property B, renaming A to B is not prevented, resulting in corrupted tree: node B is shown twice (i.e. on both rows), enabling you to expand both of them. This is the use case when the tree CRASHES, with messed-up table row indices and a nice exception in the stack trace.
|