-
Bug
-
Resolution: Duplicate
-
Blocker
-
None
-
3.3.0.Final
-
None
Since external nodes are "extremely particular" as far the JCR hierarchy that exposes them goes - i.e. they require a valid projection in a particular workspace - there are a couple of JCR operations that should only work in a limited set of cases when external nodes are present in a hierarchy:
- copy & clone should not be allowed if they take place across 2 different workspaces
- move / copy / clone within the same workspace, when the destination target exists, should only be allowed if the destination target node has the same source (i.e. belongs to the same external source) as the source node.
Without the above described validations, any one of these operation could break (in a major way) a hierarchy of external nodes.