[
https://jira.jboss.org/jira/browse/DNA-370?page=com.atlassian.jira.plugin...
]
Brian Carothers updated DNA-370:
--------------------------------
Attachment: JpaConnector_with_clone_support.patch
I have modified the CopyBranchRequest to support the concept of UUID conflict behavior in
an earlier patch. This indicates whether UUID collisions should be handled by throwing an
exception, removing the existing node and replacing it with the node from the copy, or
always using new UUIDs to avoid collisions entirely. This was pretty simple to support in
the InMemoryRepository, but required some pretty major work in JpaConnector, including
modification of the primary key of ChildEntity.
I'm attaching the JpaConnector portion of the overall work for a review and/or sanity
check.
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: 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