[dna-issues] [JBoss JIRA] Updated: (DNA-370) JcrWorkspace.clone Is Not Implemented

[Brian Carothers (JIRA)]

     [ https://jira.jboss.org/jira/browse/DNA-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-370:
--------------------------------

    Attachment: DNA-370_clone_request.patch


I tried to make workspace.update work with the existing CopyBranchRequest, but it required some changes that would have made the semantics of to(...) and into(...) ambiguous and dependent on whether the UUID conflict behavior was ALWAYS_CREATE_NEW or not.  Instead, I pulled the UUID behavior out of the CopyBranchRequest and added it into a new request - CloneBranchRequest.  This provides clear semantics for copy (always creates new UUIDs, may be between workspaces or within a single workspace, may function at the property or node level) and clone (always preserves UUIDs, only works between workspaces, may remove nodes from target workspace, only works at the node level).

The attached patch adds the new request and all of the associated changes on the graph side (adding clone operation) and the connector (implementing clone behavior for writable connectors) and modifies the workspace.clone and node.update operations accordingly.

> JcrWorkspace.clone Is Not Implemented
> -------------------------------------
>
>                 Key: DNA-370
>                 URL: https://jira.jboss.org/jira/browse/DNA-370
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>             Fix For: 0.6
>
>         Attachments: DNA-370_clone_request.patch, DNA-370_copy_behavior.patch, DNA-370_remove_items_constraint_check.patch, JpaConnector_with_clone_support.patch
>
>
> JcrWorkspace.clone is not yet implemented.  This may not be important/useful for 0.4.  AbstractJcrNode.getCorrespondingNodePath is also not yet implemented.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira