[dna-issues] [JBoss JIRA] Updated: (DNA-546) JCR Workspace and Session Imports Can Fail on JPA Connector

[Brian Carothers (JIRA)]

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

Brian Carothers updated DNA-546:
--------------------------------

    Attachment: DNA-546_simple_model_WIP.patch


Attaching a snapshot of the work in progress in case anyone's curious.  This version mostly works, although it doesn't respect References in copy or clone operations and won't enforce referential integrity.  It also has some wonky behavior around committing changes that I can't seem to figure.  This causes race conditions that lead to failures when running the L2 TCK tests.

Having given that disclaimer, the structure of the code is just about where I think it should be.  It heavily leverages the MapRepository framework and the existing Basic model.  It does differ from the other MapRepository implementations in that it creates a new MapRepository instance with every JpaSource.getConnection call - the other implementations share the same MapRepository instance across multiple connections.

Feedback is welcome as always.  My intent is to take yet another look at the race condition on the commits and then work on integrating references.

> JCR Workspace and Session Imports Can Fail on JPA Connector
> -----------------------------------------------------------
>
>                 Key: DNA-546
>                 URL: https://jira.jboss.org/jira/browse/DNA-546
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, JCR
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-546_jpa_connector_refactor.patch, DNA-546_map_node_change.patch, DNA-546_simple_model_WIP.patch
>
>
> Importing a set of nodes from an XML file will fail if one of the imported nodes has the same jcr:uuid as an existing node in the graph and removeExisting is true and the new location for the imported node and its prior location are both accessed through the same JPA connector.
> The DocumentViewImportTest is disabled (commented out) in the JPA integration test as a result of this defect.

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