Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-5529 Update mechanism improvements
  3. MAGNOLIA-1806

Refactoring / cleanup of the bootstrap classes methods

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: updatemechanism
    • Labels:

      Description

      The whole Bootstrap mechanism should be reviewed. There are currently multiple places where bootstrap is used:

      • Bootstrapper (used to bootstrap data when installing webapp)
      • BootstrapTasks (they use the deprecated ModuleUtil methods)
      • DataImporter

      All of them here and there do the same thing but do not use a common API, e.g. to:

      • resolve the target node out of the filename
      • not all support tar.gz files instead of xml files
      • etc.

      Also the usage of the ImportUUIDBehavior is sometime inconsistent used. We should probably use ImportUUIDBehavior.IMPORT_UUID_COLLISION_THROW as a default behaviour.

      In general we should introduce a main BootstrapUtil class that is commonly used by all classes mentioned above.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              gjoseph Magnolia International
              Reporter:
              gjoseph Magnolia International
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response: