Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-237

Use boot-completed notification to trigger deployment scanner "forced undeploy" scan

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • 1.0.0.Alpha15
    • None
    • Management
    • None

      The FileSystemDeploymentService "forced-undeploy" scan is scheduled based on an arbitrary 200 ms delay. Instead inject ControlledProcessStateService, install a listener, and have the listener schedule an immediate scan when it's notified that ControlledProcessState.RUNNING has been reached.

              ehugonne1@redhat.com Emmanuel Hugonnet
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: