[jbosstools-issues] [JBoss JIRA] (JBIDE-16401) OpenShift Explorer: Same connection as two different connections

Andre Dietisheim (JIRA) issues at jboss.org
Tue Jan 28 04:11:29 EST 2014


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

Andre Dietisheim resolved JBIDE-16401.
--------------------------------------

    Resolution: Rejected


@Marian: This is expected. If you have a connection to the default server, then the default server is not stored with it. We only store the username (and possibly the password). The server used for this connection is the one that your express.conf is pointing to. So once you change the server in express.conf the connection to the default server is pointing to the new (default) server in your express.conf. The connection that was using the same server but not using the default server is still pointing to the very same server (that was the default server before changing it in express.conf).
                
> OpenShift Explorer: Same connection as two different connections
> ----------------------------------------------------------------
>
>                 Key: JBIDE-16401
>                 URL: https://issues.jboss.org/browse/JBIDE-16401
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.1.1.Final
>            Reporter: Marián Labuda
>            Assignee: Andre Dietisheim
>            Priority: Minor
>
> It allows to have 2 "different" connections for one connection - 2 items in OpenShift Explorer view for same thing.
> Steps to reproduce:
> 1. EXEC: Open OpenShift explorer view
> 2. EXEC: Create connection to default OpenShift server with some credentials (checkbox for default server MUST BE checked)
> 3. ASSERT: Have connection in view with label "user server (default)"
> 4. EXEC: Open new connection shell (to create new connection)
> 5. EXEC: Uncheck checkbox for default server, but leave the same name and provide same credentials as in step 2.
> 6. EXEC: Confirm connection creation
> 7. ASSERT: There are now 2 "different" connections for same connection in OpenShift explorer view (e.g. "mlabuda at redhat.com openshift.redhat.com (default)" and "mlabuda at redhat.com openshift.redhat.com").
> Probably connections are distinguished by labels, I guess.

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



More information about the jbosstools-issues mailing list