[
https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi...
]
Viacheslav Kabanovich edited comment on JBIDE-21828 at 3/8/16 2:29 PM:
-----------------------------------------------------------------------
I also think that when an instance DeploymentResourceMapper runs buildDeployments for the
first time, it should not fire any events. Explorer has just for the first time requested
the project for children, it will get it through the mapper, and that should be all to it.
Now, in the initial creating and loading of deployments and resources cache, a lot of
events is sent. They should not be sent at all rather than be grouped. Model object should
be able to do initial loading silently, be returned as the whole and then have a listener
attached to it to report further incremental changes.
was (Author: scabanovich):
I also think that when an instance DeploymentResourceMapper runs buildDeployments for the
first time, it should not fire any events. Explorer has just for the first time requested
the project for children, it will get it through the mapper, and that should be all to it.
Now, in the initial creating and loading of deployments and resources cache, a lot of
events is sent. They should not be sent at all rather than be grouped. Model object should
be able to do initial loading silently, be returned as be whole and then have a listener
attached to it to report further incremental changes.
OpenShift Explorer view flickers when refreshing a service
----------------------------------------------------------
Key: JBIDE-21828
URL:
https://issues.jboss.org/browse/JBIDE-21828
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta2
Reporter: Xavier Coulon
Attachments: Screenshot 2016-03-08 10.32.39.png
When calling the "Refresh" command on a service, the tree view flickers because
of too many refresh calls.
Adding some traces revealed 25 calls to
{{BaseExplorerContentProvider#refreshViewer(Object)}}, which seems way too much for a
service with a single pod.
Attachement: screenshot of the OpenShift Server view, showing 2 projects, one of which
has 3 services.
Custom/added logs in the console:
{code}
Refreshing viewer from
org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
Refreshing viewer from
org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
Refreshing viewer from
org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
Refreshing viewer from
org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
Refreshing viewer from
org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
Refreshing viewer from
org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
Refreshing viewer from sample/jee-sample
Refreshing viewer from sample/jee-sample
Refreshing viewer from sample/jee-sample
Refreshing viewer from sample/jee-sample
Refreshing viewer from sample/mongodb
Refreshing viewer from sample/mongodb
Refreshing viewer from sample/mongodb
Refreshing viewer from sample/nodejs-mongodb-example
Refreshing viewer from sample/nodejs-mongodb-example
Refreshing viewer from sample/nodejs-mongodb-example
Refreshing viewer from sample/nodejs-mongodb-example
Refreshing viewer from sample/jee-sample
Refreshing viewer from sample/jee-sample
Refreshing viewer from sample/jee-sample
Refreshing viewer from sample/jee-sample
Refreshing viewer from sample/nodejs-mongodb-example
Refreshing viewer from sample/nodejs-mongodb-example
Refreshing viewer from
org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
Refreshing viewer from
org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)