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

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-14108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782371#comment-12782371 ] 

Rob Stryker commented on JBIDE-14108:
-------------------------------------

I am unable to replicate this.

Process:

1) Create as71 server
2) Start server
3) Create dynamic web project  dynweb384
4) Add/Remove to server:  dynweb384
5) verify server is published
6) Note module is deployed
7) Note in view, module is 'started'.  (This is the only part that currently fails)
8) Based on fail during 7),  right-click module, select 'start'
9) verify module is 'started', and console has output
10) right-click module, select 'stop'
11) verify module is set to 'stopped', server console has output
12) right-click module, select 'restart'
13) verify module is set to 'started', server console has output
14) right-click module, select 'restart'
15) verify module is set to 'started', server console has output

All of these steps pass except the initial part of step 7. 

Leaving this jira open to discover why the initial publish does not properly update state. 

                
> 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
>             Fix For: 4.1.x
>
>
> 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