[ https://issues.jboss.org/browse/JBIDE-16392?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-16392: ------------------------------------------ The root cause is in jbosstools-base/WizardUtils which triggers the binding to update 1) model->widget and 2) widget->model. Updating the widgets after the job was run is required since the job is synced to the wizard runnable. Before running the wizard runnable the wizard framework stores the widget states, disables all widgets and shows the progress bar. Once the runnable is finished, the wizard framework restores the widget state/enablement. The binding is not blocked by the wizard runnable/job. It possibly updated models/widgets. When the wizard framework restores the widget states (after the wizard runnable finished) it would override updated widget states and thus lead to erroneous widget states. We fix this by telling the databinding context to re-propagate model values to the widgets. Triggering updates from widgets to model is 1) unneccessary and 2) would possibly propagate erroneous widget states back to the model. We therefore eliminate these unneeded updates (widget->model) and only keep the required updates model->widget. -- 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