1 of 1 people found this helpful
I'm not sure whether it is a requirement of JCR 2.0 (I thought it was, but cannot find it in the spec), but in the very least when we implemented shareable nodes we chose to implement this limitation because it didn't seem useful to share one node multiple times under the same parent.
Actually it would be somewhat helpful for my project (I am creating shareable copy of existing node to indicate new XML tree is being edited, and in the beginning it is exact copy of previous node) but I can do a workaround of course.
But, maybe it would be interesting to compare it with other JCR implementations, as it can cause some incompatibility.
Maybe I will test this with JackRabbit in some spare time.