[
https://issues.jboss.org/browse/JBIDE-8143?page=com.atlassian.jira.plugin...
]
Andre Dietisheim commented on JBIDE-8143:
-----------------------------------------
blocking is implemented and needed in the tools so that certain functions dont invalidate
each other. So refresh is blocking a launch job since refresh and launch instance will
affect instances.
So IMHO creating the instance shoould other instance related jobs on the same cloud but
connecting with RSE should not block any more.
Do not block Deltacloud background jobs by RSE background jobs
--------------------------------------------------------------
Key: JBIDE-8143
URL:
https://issues.jboss.org/browse/JBIDE-8143
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.CR1
Reporter: Libor Zoubek
Priority: Minor
Fix For: 3.2.x
deltacloud main funcionality like starting/stopping instance, refhreshing are done via
background jobs, that is cool. The same are RSE operations (connecting to instance)
deltacloud jobs are always queued and blocked. I am not sure how background jobs in
eclipse exactly works, but we should not block operations when it is not needed.
My current usecase is:
I launch instance. When it is launched RSE is connecting in background. I cannot to
launch/refresh till RSE connects (or fails). It takes quite long time since we are waiting
for the machine to bootup etc.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira