[jbosstools-issues] [JBoss JIRA] (JBIDE-13033) When server editor is closed and opened Deployment tab is enabled even if it should not

[Rob Stryker (JIRA)]

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

Rob Stryker resolved JBIDE-13033.
---------------------------------

    Resolution: Done


Hi Martin:

Let's say you have a deployed DynWeb1.war. The editor is disabled. In order to change the value, you must:

1) Remove the module from the server
2) Click publish
3) modify value in editor to Dynweb2.war
4) save editor
5) republish with new value

The editor will not be re-enabled until step 2 is done. Step 2 ensures that {appserver_home}/standalone/deployments/DynWeb1.war is REMOVED. Then, the next publish at step 5) will publish the war as DynWeb2.war.

The end result is that dynweb.war is removed and DynWeb2.war is added. 

> But the same happens if you remove the deployment while stopped, modify the settings and then add the deployment again - we don't prevent that.

This is where you are wrong. Removing the deployment will not re-enable the editor until you publish (thus removing the remote copy with the first name). 

So, that's why it is the way it is now ;) 
                
> When server editor is closed and opened Deployment tab is enabled even if it should not
> ---------------------------------------------------------------------------------------
>
>                 Key: JBIDE-13033
>                 URL: https://issues.jboss.org/browse/JBIDE-13033
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 4.0.0.Beta2
>         Environment: JBT 4.0.0.Beta2 B43
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.0.0.CR1
>
>
> Not sure how you control the disabling of the Deployment tab, but it doesn't always work correctly.
> When it's disabled and you reopen (close&open) the server editor it is enabled again.
> Also the comment at the top of the Deployment tab says:
> "Settings on this page may only be modified if the server has 0 modules and is fully synchronized."
>  - this is not totally accurate - should have something like: "or the server is stopped"

--
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