[
https://issues.jboss.org/browse/JBIDE-22471?page=com.atlassian.jira.plugi...
]
Dmitry Bocharov commented on JBIDE-22471:
-----------------------------------------
Latest research results.
In cases when connection stays "Loading" the following happens:
1) BaseExplorerContentProvider.refreshViewer() is called
2) AbstractTreeViewer.internalRefresh(Object, boolean) is called
3) Widget[] items = findItems(element); returns an empty array of child nodes for
connection, because there are no elements in elementMap (see StructuredViewer.findItems()
method)
It means that it has nothing to refresh.
In cases when everything works fine, there elements in elementMap and everything refreshes
fine.
So for some reasons the child nodes are late to be loaded to the widget sometimes,
Explorer: connection (without stored token) stays "Loading"
after I provided the token
--------------------------------------------------------------------------------------
Key: JBIDE-22471
URL:
https://issues.jboss.org/browse/JBIDE-22471
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.0.Alpha2
Reporter: Andre Dietisheim
Assignee: Dmitry Bocharov
Priority: Critical
Labels: explorer, openshift_v3
Fix For: 4.4.0.Final
Attachments: explorer-not-refreshed.png
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)