Uploaded image for project: 'Alfresco'
  1. Alfresco
  2. ALF-6565

Explorer UI allows duplication of Replication targets which in effects breaks Alfresco

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Security Level: external (External user)
    • Labels:
      None
    • Environment:
    • Resource:
      External

      Description

      My install is 3.4.b Community on CentOS 5.5 x86.

      Explorer UI allows one to duplicate replication job targets in Repository> Data Dictionary> Transfers> Transfer Target Groups> Default Group by using "copy/paste space" tools from the dropdown above the space browser. Effect is that on consecutive starts of Alfresco will fail due to:

      ::ERROR [org.springframework.web.context.ContextLoader] Context initialization failed
      ::org.alfresco.service.cmr.repository.DuplicateChildNodeNameException: Duplicate child name not allowed: Internal Target

      Where "Internal Target" is metadata "name" of replication target since space names are different.

      I beleive this to be a showstopper for a tinkering user (like myself) since Explorer UI, the only trivial way to fix the issue cannot be started so the user has no simple access to the repository.

      Proposed remedy:
      UI should display an error message on attempts to duplicate elements that cannot and shouldn't be duplicated (ie where metadata elements sould be unique) and disallow/abort action. Especially cases like this where the metadata itself isn't editable through UI. Upon startup (if by some odd combination of tinkering and legitimate actions user managed to create duplicates) all nodes apart from the "factory default" one should be ignored and exceptions should be logged.

        Attachments

          Activity

            People

            • Assignee:
              closedissues Closed Issues
              Reporter:
              bmarkovic Bojan Markovic (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Date of First Response:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day, 4 hours
                1d 4h