FULL PRODUCT VERSION :
java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)

A DESCRIPTION OF THE PROBLEM :
SwingWorker is described in the JavaTutorial and is used
by many programmers. Still SwingWorker is not part of
the "official" JDK.
I'm sure there are many classes in the JDK that are not as
frequently used as SwingWorker.

EXPECTED VERSUS ACTUAL BEHAVIOR :
Add SwingWorker to the JDK

This bug can be reproduced always.

CUSTOMER WORKAROUND :
You can always add SwingWorker to your own program (as you
could with most classes in the JDK)
(Review ID: 146315) 
======================================================================

N/A

Please refer to
http://ccc.sfbay.sun.com/4681682
and 
http://sa.sfbay.sun.com/projects/swing_data/mustang/4681682

for the implementation details and the API
  xxxxx@xxxxx   2005-05-19 17:34:54 GMT

Operations which lasts for more than a second in Swing apps 
should in most cases be using SwingWorker.  Why is it *still* 
not part of Swing?

I created an extension to SwingWorker called ComponentUpdateThread that takes care of addition items for the user such as disabliing buttons during operations etc.  It also provides the use of Generics in construct().  The swingutil.dev.java.net project is where this class can be found.

Is there any reason not to add SwingWorker?
It is annoying to have to add vendor supplied framework code to applications...

I think that SwingWorker should be part of the JDK

How large is the SwingWorker jar file? I am planning to distribute my app using Java Web Start and am trying to make the download as small as possible, to help slow dialup users.

Should be usefull to add not only swingworker (referring to asyncronous model), but also a system that permits to use the synchronous model. See foxtrot for details (see http://foxtrot.sourceforge.net/docs/introduction.php). This model is more flexible and permits an easy way to manage time consuming events.

I also think the SwingWorker should be part of JDK.

SwingWorker is very useful when building Swing GUIs and I think it should be part of JDK.

i give my vote to SwingWorker

I think SwingWorker should be part of JDK.

I give my vote in favour of this proposal.

cchhaanndduu:

I give my vote to SwingWorker class to be included in JDK. This is very useful in the programs where the initialisation of the GUI takes long duration.

cchhaanndduu@gmail.com

I also think the SwingWorker should be part of JDK.