Uploaded image for project: 'Atlas'
  1. Atlas
  2. ATLAS-2220

Active state change listener order should be predictable

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.8.2, 1.0.0
    • atlas-core
    • None

    Description

      Currently 5 handlers register for notification on Atlas instance state change events. The order in which these handlers are not defined, due to use of Set<> to collect the handlers. This needs to be updated to make the handler calling order predictable.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            madhan Madhan Neethiraj
            madhan Madhan Neethiraj
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment