[jbosstools-issues] [JBoss JIRA] (JBIDE-8276) Suggest removing related servers when removing RSE connection

[Rob Stryker (JIRA)]

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

Rob Stryker resolved JBIDE-8276.
--------------------------------

    Fix Version/s: 4.1.0.Beta1
                       (was: 4.1.x)
       Resolution: Done


I'm closing this issue as out of date. My findings are as follows:

1) Our server editor code already updates the combo list of possible hosts when a host is added or removed. 

2) AN attempt to start the server first necessitates a publish. THe publish properly fails when a remote host is missing.

3) The deletion of a host does not use a UI capable of allowing participants, so we can only be involved as a listener. 

4) In the rare chance that the server does not attempt to publish and fail, I have added 2 lines to properly check and error during launch.

Unfortunately, we will not be suggesting servers be deleted at this time. So in some ways, this issue is also a 'wont-fix'
                
> Suggest removing related servers when removing RSE connection
> -------------------------------------------------------------
>
>                 Key: JBIDE-8276
>                 URL: https://issues.jboss.org/browse/JBIDE-8276
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: server
>            Reporter: Libor Zoubek
>            Assignee: Rob Stryker
>             Fix For: 4.1.0.Beta1
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> If a server is created using deltacloud it is related to RSE connection. If user removes RSE Connection and then tries to start server, he gets error about possibly deleted connection, which is fine. Is it possible to suggest him deleting related servers when deleting RSE Connection like it is when server runtime is deleted?

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