jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] [Created] (JCR-3068) IMPORT_UUID_COLLISION_REPLACE_EXISTING import should not fail for duplicate UUIDs
Date Mon, 12 Sep 2011 12:47:09 GMT
IMPORT_UUID_COLLISION_REPLACE_EXISTING import should not fail for duplicate UUIDs
---------------------------------------------------------------------------------

                 Key: JCR-3068
                 URL: https://issues.apache.org/jira/browse/JCR-3068
             Project: Jackrabbit Content Repository
          Issue Type: Bug
          Components: jackrabbit-core
            Reporter: Julian Reschke
            Priority: Minor


ConcurrentImportTest exercises concurrent imports with nodes having the same UUID.

The spec says for this case:

"IMPORT_UUID_COLLISION_REPLACE_EXISTING: If an incoming non-shareable node has the same identifier
as a node already existing in the workspace, then the already existing node is replaced by
the incoming node in the same position as the existing node." 

<http://www.day.com/specs/jcr/2.0/11_Import.html#11.8.3%20Replace%20Existing%20Node>

So throwing an InvalidItemStateException is not correct.

(The test class was introduced for tracking down a different type of issue - JCR-2272 - so
I'll leave it alone for now)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message