[
https://issues.apache.org/jira/browse/JCR-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409700#comment-13409700
]
Randall Hauch commented on JCR-3380:
------------------------------------
Julian,
Good question. Moving shareable nodes is not explicitly disallowed (or at least
I can't find it). And since much of the specification addresses shareable nodes
by describing how the behavior of a feature differs for shareable nodes (e.g.,
Chapter 14 "Shareable Nodes" specifically mentions the how importing,
exporting, removing, copying, observation, locking, constraints, versioning,
restore, and query are all affected by/for shareable nodes), my reading is that
shareable nodes are allowed.
Interestingly, the tests don't even try to move nodes that have already been
shared. Instead, they simply create a node, add the "mix:shareable" mixin, and
then try to move that node.
> TCK tests for shareable nodes assume moving shareable nodes is not supported
> ----------------------------------------------------------------------------
>
> Key: JCR-3380
> URL: https://issues.apache.org/jira/browse/JCR-3380
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-tests, JCR 2.0, test
> Affects Versions: 2.5
> Reporter: Randall Hauch
> Fix For: 2.5.1, 2.6
>
>
> There are two tests in ShareableNodeTest that assume that an implementation
> does not support moving shareable nodes. This is inconsistent with what is
> required by JSR-283.
> 1) testMoveShareableNode assumes that the implementation does not support
> moving nodes that are 'mix:shareable' (even when they are not yet shared)
> using Workspace.move(...).
> 2) testTransientMoveShareableNode makes a similar assumption to #1, except
> that it uses the Session.move(...) operation.
> Both of these test should be changed to allow an implementation to either not
> support the operation (e.g., Jackrabbit) or to properly check the results.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
