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

org/openmrs/scheduler/timer/TimerSchedulerServiceImpl.java

    XMLWordPrintable

Details

    • Undetermined

    Description

      TODO Make sure this is the desired behavior

      Location:

      https://github.com/openmrs/openmrs-core/blob/2.2.0/api/src/main/java/org/openmrs/scheduler/timer/TimerSchedulerServiceImpl.java#L208

       

      TODO Do we ever want the same task definition to run more than once?

      Location:

      https://github.com/openmrs/openmrs-core/blob/2.2.0/api/src/main/java/org/openmrs/scheduler/timer/TimerSchedulerServiceImpl.java#L209

       

      TODO change the index for the scheduledTasks map to be the TaskDefinition rather than the ID

      Location:

      https://github.com/openmrs/openmrs-core/blob/2.2.0/api/src/main/java/org/openmrs/scheduler/timer/TimerSchedulerServiceImpl.java#L346

       

      TODO Look into java.util.concurrent.TimeUnit class.

      Location:

      https://github.com/openmrs/openmrs-core/blob/2.2.0/api/src/main/java/org/openmrs/scheduler/timer/TimerSchedulerServiceImpl.java#L444

       

      TODO Remove this from global properties. This is a constant value that should never change.

      Location:

      https://github.com/openmrs/openmrs-core/blob/2.2.0/api/src/main/java/org/openmrs/scheduler/timer/TimerSchedulerServiceImpl.java#L445

       

      org.openmrs.scheduler.SchedulerService#getStatus(java.lang.Integer) TODO internationalization of string status messages

      Location:

      https://github.com/openmrs/openmrs-core/blob/2.2.0/api/src/main/java/org/openmrs/scheduler/timer/TimerSchedulerServiceImpl.java#L507

      Gliffy Diagrams

        Attachments

          Issue Links

            relates to

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. TRUNK-324 Go through the TODO items code and create tickets out of them

            • Should - Issue should be completed for its milestone; however, will not delay the milestone.
            • Ready for Work

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. TRUNK-6087 COPY: Go through the TODO items code and create tickets out of them

            • Should - Issue should be completed for its milestone; however, will not delay the milestone.
            • Needs Assessment

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. TRUNK-6108 COPY: Go through the TODO items code and create tickets out of them

            • Should - Issue should be completed for its milestone; however, will not delay the milestone.
            • Needs Assessment

            Activity

              People

                Unassigned Unassigned
                isaaclin isaac lin
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: