[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_copy_behavior.patch


Applied the attached patch (DNA-370_copy_behavior) to add support for UuidConflictBehavior in the graph layer and each of the three connectors that currently support writes.  This includes the previous patch to modify the JPA connector and required some fairly heavy modifications of the JBoss Cache connector to support efficient look-ups by UUID.

The patch also corrects some configuration to allow the JR TCK clone tests to start working.  This will result in one false negative in the nightly TCK compatibility build, as there is a clone test that assumes the repository supports locking.

There is still some work left to be done to fully support clone.  If removeExisting is true, the JCR layer must first identify any conflicts and speculatively remove them to make sure that removing the existing nodes won't violate type constraints.  This check cannot be done at the graph or connector layer, as those layers are unaware of the JCR typing semantics.  Additionally, the update method must still be implemented.

> 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_copy_behavior.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