Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-6712

Light module dependency check and decoration ordering should happen at runtime

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Won't Do
    • Neutral
    • None
    • 5.4.7
    • None
    • None

    Description

      Currently the module descriptor for light modules is only evaluated at system startup, which is consistant with maven modules. This means that check for dependencies, and the ordering of the decorators is only set at system startup.

      A key value of light modules is that they take effect as soon as they are added to a running instance. This should also apply to the mechanisms tied to the module descriptor.
      (It's correct that the module descriptor is also evaluated at system startup.)

      When a light module is detected on a running instance:

      • If the module depends on some module/version that is not present, an error should be logged and a pulse message sent. (to users with superuser role?)
      • The application order of the decorators should be re-evaluated based on the dependencies and definitions reloaded if necessary.

      When a light module is removed from a running instance:

      • The application order of the decorators should be re-evaluated based on the dependencies and definitions reloaded if necessary.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              czimmermann Christopher Zimmermann
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Task DoD