Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JBIDE-18247 : delay remote variable resolution to when necessary #293

Merged
merged 1 commit into from
Sep 19, 2014
Merged

JBIDE-18247 : delay remote variable resolution to when necessary #293

merged 1 commit into from
Sep 19, 2014

Conversation

fbricon
Copy link
Member

@fbricon fbricon commented Sep 18, 2014

When displaying Central, ProxyWizardManager and RefreshBuzzJob instantiations trigger fetching of remote resources (ide-config.properties), that could block the UI for an indefinite amount of time.
The values being looked up are not required until later, by methods running in Jobs, so the current fix consists in performing the lookups only when necessary and when it's safe to do it.

The fix is certainly not ideal, other parts of the code calling PropertiesHelper.getPropertiesProvider().getValue(...) might require better handling as well, but this would require major refactoring at the foundation level (introducing/handling timeouts).

Until a better redesign can be performed, the current fix makes Central not blocking the UI, as expected. Some jobs keeps running for a very long time in the background but they can be cancelled any time.

Signed-off-by: Fred Bricon fbricon@gmail.com

When displaying Central, ProxyWizardManager and RefreshBuzzJob instantiations trigger fetching of remote resources (ide-config.property), that could block the UI for an indefinite amount of time.
The values being looked up are not required until later, by methods running in Jobs, so the current fix consists in performing the lookups only when necessary and when it's safe to do it.

The fix is certainly not ideal, other parts of the code calling PropertiesHelper.getPropertiesProvider().getValue(...) might require better handling as well, but this would require major refactoring at the foundation level (introducing/handling timeouts).

Until a better redesign can be performed, the current fix makes Central not blocking the UI, as expected. Some jobs keeps running for a very long time in the background but they can be cancelled any time.

Signed-off-by: Fred Bricon <fbricon@gmail.com>
@dgolovin
Copy link
Member

+1

@fbricon fbricon merged commit e895c92 into jbosstools:jbosstools-4.2.x Sep 19, 2014
@fbricon fbricon deleted the JBIDE-18247-42x branch September 19, 2014 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants