Uploaded image for project: 'Jackrabbit Content Repository'
  1. Jackrabbit Content Repository
  2. JCR-1128

XML import always throws ItemExistsException when trying to overwrite existing nodes

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 1.0, 1.0.1, 1.1, 1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.3, 1.3.1
    • 1.3.3
    • JCR API
    • None

    Description

      According to the JCR-API, it should be possible to govern the import of XML serialized referenceable nodes in case of UUID collision. Unfortunately, the UUID conflict is handled too late during import, an ItemExistsException is always thrown beforehand due to not allowed same-name-siblings.

      Simply try to import a previously exported referenceable node twice, providing either

      • ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING or
      • ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING.

      This will fail and result in an ItemExistsException.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JCR-1512 Incorrect check for replace when importing item with colliding id

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. OAK-9541 ItemExistsException: "Node with the same UUID exists" thrown during SysView import with existing different UUID

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed

          Activity

            People

              stefan@jira Stefan Guggisberg
              hwong Honwai Wong
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: