Uploaded image for project: 'OpenMRS Core'
  1. OpenMRS Core
  2. TRUNK-4668

When a module is started, all its dependent modules should be started

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Should
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Core 2.1.0
    • Component/s: None
    • Labels:
    • Complexity:
      Medium

      Description

      The module engine needs to support starting all dependent modules when a module is started.

      Questions

      Should this happen automatically, or do we require confirmation? (e.g. a boolean parameter in the API call indicating whether to recurse)

      Acceptance Criteria

      1. If you try to start a module, and all modules it depends on are installed in the OpenMRS system, but some of them are not started, all the modules are started together
        • In this scenario, the OpenMRS/Spring context must be refreshed just one time (not once per module)
      2. If you try to start a module, and it depends on any modules that are not installed, then the UI should show an error message, but no expensive reload/refresh operation should happen (and no module states should be changed)

        Gliffy Diagrams

          Attachments

            Issue Links

              Attachments-Category-Modification

                Activity

                  People

                  • Assignee:
                    ivange94 Ivange Larry Ndumbe
                    Reporter:
                    wyclif Wyclif Luyima
                    Designated Committer:
                    Daniel Kayiwa
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    5 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: