Uploaded image for project: 'Jackrabbit FileVault'
  1. Jackrabbit FileVault
  2. JCRVLT-124

Inconsistent behaviour of ImportMode.MERGE

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 3.1.28
    • Fix Version/s: 3.4.6
    • Component/s: Misc
    • Labels:
      None

      Description

      In [0], it is stated that with ImportMode.MERGE option;

      Existing content is not modified, i.e. only new content is added and none is deleted or modified.

      however in the code [1], it imports the content only “if node is an authorizable or ACL”.
      Is it a documentation issue or implementation issue ? Which behavior the customer should expected?

      Steps to reproduce are available:

      1. Install example-1.zip
      2. Install example-2.zip

      Expected: apps/i18n/en/example2 should be created
      Outcome: Node is not created

      [0] - http://jackrabbit.apache.org/filevault/importmode.html

      [1] org.apache.jackrabbit.vault.fs.impl.io.GenericArtifactHandler.accept(WorkspaceFilter, Node, String, ArtifactSetImpl)

      if (name.length() == 0 || parent.hasNode(name)) {
                      if (wspFilter.getImportMode(path) == ImportMode.MERGE) {
                          // do import the content if node is an authorizable or ACL
      

        Attachments

        1. example-2.zip
          11 kB
          Ilyas Türkben
        2. example-1.zip
          11 kB
          Ilyas Türkben

          Issue Links

            Activity

              People

              • Assignee:
                tripod Tobias Bocanegra
                Reporter:
                tuerkben Ilyas Türkben
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: