Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 347791 - Job Handling is different in Swing and SWT
Summary: Job Handling is different in Swing and SWT
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Scout (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-31 10:10 EDT by Matthias Zimmermann CLA
Modified: 2021-08-19 11:28 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Zimmermann CLA 2011-05-31 10:10:16 EDT 
Swing and SWT-Jobs do not behave equally. 

When aborting a Job in Swing the ClientJobs are aborted. One of those ClientJob has typically started a HttpBackgroundJob and waits for its completion in a while loop. When aborting that job the HttpBackgroundjob is aborted too.

Aborting Jobs in SWT (EclipseRCP) is usually done by using a progress view. A progress view shows all jobs with the property system=false. Only the HttpBackgroundJob has currently set this flag to false. So in case of SWT the HttpBackgroundJob is aborted instead of the ClientJob which has started the backgroundJob.

This behaviour leads to the problem that when aborting a job in SWT a wrong error message is displayed. Instead of InterruptedException a SocketException is thrown.

Furthermore the properties system and user of the Job seem to be ignored by the Swing-UI.

It would be nice if the behaviour of swing and swt were the same.
Comment 1 Matthias Zimmermann CLA 2011-05-31 10:11:01 EDT 
fixed on 5.3.11, #101303
Comment 2 Matthias Zimmermann CLA 2011-06-28 09:13:26 EDT 
shipped with eclipse scout 3.7.0