[jbosstools-issues] [JBoss JIRA] (JBIDE-18037) Server Adapter wizard, Connection wizard: Cannot select other connection in creating a new server adapter than the first one in case of not connected connection

[Andre Dietisheim (JIRA)]

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

Andre Dietisheim updated JBIDE-18037:
-------------------------------------
    Labels: connection_wizard openshift_v2 server_adapter_wizard  (was: connection_wizard server_adapter_wizard)


> Server Adapter wizard, Connection wizard: Cannot select other connection in creating a new server adapter than the first one in case of not connected connection
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-18037
>                 URL: https://issues.jboss.org/browse/JBIDE-18037
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.2.0.Beta3
>            Reporter: Marián Labuda
>            Priority: Minor
>              Labels: connection_wizard, openshift_v2, server_adapter_wizard
>             Fix For: LATER
>
>         Attachments: openshift_explorer.png, server_adapter_wizard.png
>
>
> When creating a new server adapter there is a wizard where user can choose existing connection in case of not connected connection (e.g. after restarting Eclipse/JBDS).
> !server_adapter_wizard.png!
> Problem is when you are not connected to the first connection in OpenShift explorer. Than the wizard preselect the first one connection from OpenShift Explorer and others are missing in the selection - mine OpenShift explorer contains 3 connections but in the wizard mentioned above is only first one listed in the combo box.
> !openshift_explorer.png!
> There should be option to choose any connection and on the next wizard pages this connection could be preselected.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)