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


Attached patch (DNA-546_mostly_working.patch) that provides a mostly working implementation of a new model for the JPA connector.  The model passed all of the connector reading and writing tests except for a single test that tracks graph-level references.  This is not surprising as the only outstanding feature on the model is the equivalent of the ReferenceEntity and referentialIntegrityEnforced code in the Basic model.  I have overridden that test for now so that the CI build will work.

This patch also does not include a TCK integration test.  That is because it will not pass the TCK integration test unless the JcrRepository.WORKSPACES_SHARE_SYSTEM_BRANCH is set to false.  When the flag is set to false, the same L1, L2, and locking TCK tests pass for this connector as pass for (as an example) the InMemoryRepository.  However, this flag manifestly cannot be changed to false in a production environment, so sorting out this issue is a major priority.

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