[ https://issues.jboss.org/browse/JBIDE-23210?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-23210: ----------------------------------------------- That is what happens here: NewApplicationWizard.init(workbench, selection) does two calls (1) setConnection(connection); (2) model.setProject(resource.getProject()); While the first call is performed, on event from the change of connection, method DeployImageWizardModel.initModel(connection, project, loadResources) is called with project = null, because the call (2) is not yet done. Method initModel starts job "Loading projects..." which is to set projects and select default project. Now, we have the race of job and main thread. Main usually wins, makes its call (2), after which job sets default project to DeployImageWizardModel which is not synchronized with project instance in NewApplicationWizardModel. So, user sees correctly selected project in combo, taken from NewApplicationWizardModel, while DeployImageWizardModel inconspicuously holds wrong default project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)