[jbosstools-issues] [JBoss JIRA] (JBIDE-16939) OpenShift application creation should not lock the UI while waiting for DNS to propagate

[Andre Dietisheim (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-16939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12957468#comment-12957468 ] 

Andre Dietisheim edited comment on JBIDE-16939 at 3/28/14 3:39 PM:
-------------------------------------------------------------------

Hard to know what you really mean here. All (beside maybe forgotten parts?) operations are executed in the background. Can you please be more precise when exactly you experience freezing in the OpenShift tooling and what tells you that the freeze you see is DNS related?. I dont see any freezing after completion of the application wizard.
What version of the tooling are you using ("Affects Version")?
                
      was (Author: adietish):
    Hard to know what you really mean here. All (beside maybe forgotten parts?) operations are executed in the background. Can you please be more precise when exactly you experience freezing in the OpenShift tooling. I dont see any freezing after completion of the application wizard.
                  
> OpenShift application creation should not lock the UI while waiting for DNS to propagate
> ----------------------------------------------------------------------------------------
>
>                 Key: JBIDE-16939
>                 URL: https://issues.jboss.org/browse/JBIDE-16939
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: openshift
>            Reporter: Lincoln Baxter III
>
> After completing the OpenShift -> New Application wizard, the UI locks while Eclipse waits for the OpenShift operation to complete. Many OpenShift operations (including application creation) can take quite a while, and it should be able to be moved to the background, allowing the user to continue working while waiting.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira