[jbosstools-issues] [JBoss JIRA] (JBIDE-21590) Explorer: OpenShift connection is not refreshed upon project deletion

[ https://issues.jboss.org/browse/JBIDE-21590?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21590: ----------------------------------------------- [~jcantrill], it is the role of scheduling rules to prevent the race condition at least for actions started from Eclipse. Let us compare to Project Explorer handling resources. One also can call delete resource and refresh its parent. Of course, local disk is much more responsive than a remote server, but we can emulate the delay in debugger by stopping inside 'delete resource' job right after the file is physically removed from disk. Will that put workspace into an invalid state? - no, because job manager is told that 'delete resource' and 'refresh that resource's parent' job are conflicting, and one should wait for completion of the other. But, is an invalid space ever possible in the workspace? - yes, when you delete or modify a file on disk outside of Eclipse, in this case some actions, like global search, inform us that they could not complete successfully, because some resources are out of sync. So, there is no much difference between Project Explorer + Resources on local disk and OpenShift Explorer + resources on remote server. Jobs started from Eclipse should inform job manager by scheduling rules about conflicting, and actions should be prepared that they may be invoked on a resource that is out of sync (because it can be caused by changes done externally on server). -- This message was sent by Atlassian JIRA (v6.4.11#64026)