Andre Dietisheim created JBIDE-21153:
----------------------------------------
Summary: Use extension in OpenShiftCoreUIIntegation
Key: JBIDE-21153
URL:
https://issues.jboss.org/browse/JBIDE-21153
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.3.1.Beta1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.3.1.Beta1
the Connection class resides in the openshift core plugin. It happens that connections
need to pop up dialogs in order to ex. let the user confirm ssl signatures or provide a
token/credentials. To allow class to do this we have the OpenShiftCoreUIntegration
currently, which is initialized by the activator in org.jboss.tools.openshift.ui by
injecting the dialogs into OpenShiftCoreUIIntegration. This works fine as long as some UI
is started before the connection gets activated. When creating a server adapter this
doesnt work any more. The openshift server adapter resides in
org.jboss.tools.openshift.core only, there's no openshift UI involved. The connection
is therefore not able to prompt the user for a new token etc.
We therefore have to change the current injection based approach (ui injects dialogs into
core) by a extension point that the core is querying as soon as it requires some UI.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)