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

When a module activator's started() method throws an exception, the module should stop

    XMLWordPrintable

    Details

      Description

      Currently, if a module's activator's started() method throws an exception, that just goes to the log, while the module ends up being started.

      This is wrong. If a module's activator's started() method throws an exception, this failure should be loud. It's certainly meaningful, and modules shouldn't be running if they were unable to complete their started() method, as this is really an illegal state.

      TODO: the module framework should catch activator.started() exceptions, and if one occurs it should stop the module.

      See https://groups.google.com/a/openmrs.org/d/topic/dev/s8_3xAGWrS4/discussion

        Gliffy Diagrams

          Attachments

            Activity

              People

              Assignee:
              raff Rafal Korytkowski
              Reporter:
              darius Darius Jazayeri
              Votes:
              3 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 2 hours Original Estimate - 2 hours
                  2h
                  Remaining:
                  Time Spent - 30 minutes Remaining Estimate - 4 hours
                  4h
                  Logged:
                  Time Spent - 30 minutes Remaining Estimate - 4 hours
                  30m