[jbosstools-issues] [JBoss JIRA] (JBIDE-17395) Run on server does not work if server is stopped (management operations)

[Rob Stryker (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-17395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBIDE-17395.
---------------------------------

    Resolution: Done


The client (which opens the web browser, basically), already waits for a few things.    

 1) It waits for server to be started
 2) It waits for the server to respond that the module is deployed properly via mgmt request

The workflow of what's happening here is:
  1) Run as -> Run on server
  2) The server tries to publish, but is told by my delegate that we cannot publish to a stopped server
  3) The server is started
  4) The 'client' is given control, and waits for confirmation the module is ready
 
The patch which has been committed will, during step 4), check if the module is 'synchronized'. In the above use case, the module is *not* synchronized, since we did not attempt to actually publish it. 

When the client learns the module isn't even synchronized, we issue a publish request. 

The result is pretty fast and looks good. Pushed to b3. 

> Run on server does not work if server is stopped (management operations)
> ------------------------------------------------------------------------
>
>                 Key: JBIDE-17395
>                 URL: https://issues.jboss.org/browse/JBIDE-17395
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.0.Beta2
>         Environment: JBT 4.2 master (Beta3-v20140522-2026-B498)
> EAP 6.2 / WildFly 8.0/8.1
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.2.0.Beta3
>
>
> When you use "Run on server" on a project and the server is stopped and uses management operations, it won't work - meaning the server will start, server view will show the project as deployed, but it won't be actually deployed and when the browser opens, it will 404.
> I checked that this affects both EAP 6.2 and WildFly (and most probably other similar servers, too).



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)