[jbosstools-issues] [JBoss JIRA] (JBIDE-17621) When you add a runtime to a runtime-less server, you cannot remove it again

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-17621:
-------------------------------------

I think removing the runtime information from the server editor is not optimal. Users may be curious what runtime is currently selected.  However, making it a combo and able to be changed adds a lot more complication to a widget that's already quite complicated. 

I propose to keep the runtime information there, complete with hyperlink (to edit the runtime's details) and a disabled text box (to display the current runtime). This, I feel, provides the easiest opportunity to keep the information visible while still editable only in one place. 

As for the edit-profile / behavior wizard, I don't think it's smart to just add a "(no runtime)" element, for a few reasons. First, these are not forbidden characters in a runtime's name, so a user could theoretically create a runtime named (no runtime) and then confuse things. I'll be leaving that UI as it currently is.

> When you add a runtime to a runtime-less server, you cannot remove it again
> ---------------------------------------------------------------------------
>
>                 Key: JBIDE-17621
>                 URL: https://issues.jboss.org/browse/JBIDE-17621
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server, upstream
>    Affects Versions: 4.2.0.Beta2
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.2.0.CR1
>
>
> When you create a remote server without a runtime and then open the server editor and click the runtime drop down menu, a suitable runtime will be selected. But once you do that, you can no longer revert that action (once you save the editor).
> Clearly, there needs to be a new item in the drop down menu called <none> or something similar.
> Credit for spotting this bug goes to [~ljelinko] ;)



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)