[
https://issues.jboss.org/browse/JBIDE-25814?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-25814:
------------------------------------------
[~rob.stryker] we have the concept of the most recently used connection:
{code:title=ConnectionsRegistry}
public IConnection getRecentConnection() {
return recentConnection;
}
{code}
The connection wizard is using this most recently used connection if none was provided
that should be selected.
{code:title=ConnectionWizard}
public ConnectionWizard() {
this(ConnectionsRegistrySingleton.getInstance().getRecentConnection(),
NEW_CONNECTION_TITLE);
}
{code}
The connection that one is using to connect is stored upon connecting:
{code:title=ConnectionWizardPageModel}
public IStatus connect() {
...
ConnectionsRegistrySingleton.getInstance().setRecent(connection);
...
}
{code}
Server adapter wizard: should use selected or recent connetion, not
simply the 1st in the list
----------------------------------------------------------------------------------------------
Key: JBIDE-25814
URL:
https://issues.jboss.org/browse/JBIDE-25814
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.5.3.AM2
Reporter: Andre Dietisheim
steps:
# ASSERT: have several connections in the OpenShift explorer (ex. CDK, OpenShift online)
# EXEC: launch new application wizard via File > New > Other > OpenShift >
OpenShift Application
# ASSERT: Connection selection page pops up
# EXEC: select your 2nd connection, get to the next page. But then, cancel, dont get any
further.
# EXEC: launch server adapter wizard via File > New > Other > Server >
OpenShift > OpenShift 3 Server adapter
# ASSERT: Connection selection page pops up
Result:
the connection selection page has the 1st connection selected, not the one that we used
lately
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)