[jbosstools-issues] [JBoss JIRA] (JBIDE-14108) EAP6.1 Server Runtime, per-module Start/Stop greyed out when should be usable

[Darryl Miles (JIRA)]

Darryl Miles created JBIDE-14108:
------------------------------------

             Summary: EAP6.1 Server Runtime, per-module Start/Stop greyed out when should be usable
                 Key: JBIDE-14108
                 URL: https://issues.jboss.org/browse/JBIDE-14108
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: server
    Affects Versions: 4.1.0.Alpha1
         Environment: Windows7 EAP6.1 Juno-SR2
            Reporter: Darryl Miles


EAP6.1 Server Runtime, per-module Start/Stop greyed out when should be usable.


I configure and start EAP 6.1.

While it is running I use Add/Remove... to add an EAR project (maybe any deployable project will work)

I wait for it to bootup.

Once booted I use the action "Stop" or "Restart".

This action occurs but the state of the dialog is not update.

What should happen is the "Start" button should become available again.

The "Restart" action seems to always be available.  But even using it when it was stopped does not result in the "Stop" action from being available again.

Only the first use of adding the module the buttons work as expected.




I think the server runtime connector should have be able to guess the current status of each module by looking for all the files expected:

*.deployed (means started, so Restart and Start are valid action)
*.isdeploying (means it is on the way up)
*.undeployed (means stopped)
*.isundeploying (I never saw this before, but I guess it may exist)
*.failed (means stopped)
No file found (means stopped)

This means it is possible to poll the state of these files always and update accordingly.




Also there is no ICON picture next to the Restart next to the per-module setting.  I am sure there is one around somewhere and the colour and grey of this icon give good indicator the action is possible or not.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira