Please note that this page has moved to: http://www.javacreed.com/swing-worker-example/.
Java provides a neat way to carry out long lasting jobs without have to worry about threads and hanging the application. It's called SwingWorker. It's not the latest thing on Earth (released with Java 1.6) and you may have already read about it. What I never came across was a practical example of the swing worker.
Swing Worker
SwingWorker is an abstract class which hides the threading complexities from the developer. It's an excellent candidate for applications that are required to do tasks (such as retrieving information over the network/internet) which may take some time to finish. It's ideal to detach such tasks from the application and simply keep an eye on their progress. But before we hit the road and start working with the swing worker we have to see what "eye" are we going to put on our worker so to say.
The following example illustrates a simple empty worker that will return/evaluate to an integer when the given task is finished. It will inform the application (the "eye" thing) with what's happening using objects of type string, basically text messages.
import javax.swing.SwingWorker;
public class MyBlankWorker extends SwingWorker<Integer, String> {
// Some code must go here
}
The string worker class provides two place holders (generics). The first one represents the type of object returned when the worker has finished working. The second one represents the type of information that the worker will use to inform (update) the application with its progress. The swing worker class also provides means to update the progress by means of an integer which has nothing to do with the two generics mentioned before.
Practical Example
Example: Let say we need to find the number of occurrences of a given word with in some documents. So we would be writing something like:
import java.io.File;
import javax.swing.SwingWorker;
public class SearchForWordWorker
extends SwingWorker<Integer, String> {
private final String word;
private final File[] documents;
public SearchForWordWorker(String word, File[] documents){
this.word = word;
this.documents = documents;
}
@Override
protected Integer doInBackground() throws Exception {
int matches = 0;
for(int i=0, size=documents.length; i<size; i++){
// Update the status: the keep an eye on thing
publish("Searching file: "+documents[i]);
try {
// Do the search stuff
// Here you increment the variable matches
} finally {
// Close the current file
}
// update the progress
setProgress( (i+1) * 100 / size);
}
return matches;
}
}
The first thing that comes into mind is where is the text "Searching file: ..." is going? The swing worker class provides another method called process which accepts a list (of type string in our case) and used to process the published information (which can be an object of any kind). Overriding this method, allows us to take full control of this information.
@Override
protected void process(List<String> chunks){
for(String message : chunks){
System.out.println(message);
}
}
The above example is not much useful. We may need to update the status bar of an application or the text of the progress bar or a label sitting somewhere in the application. Since we may be monitoring this worker from various UI components, ideally we add a level of isolation between the worker and the UI components. In many examples, the worker was fed UI components as constructor parameters. I would go for interfaces instead to make the design pluggable when possible.
In other occasions a worker may be used to populate a table which information is coming from a slow source. In this case we may use the table model as one of the workers parameter and the array of objects representing the row. The following example makes use of the default table model as the design is simpler.
import java.util.List;
import javax.swing.SwingWorker;
import javax.swing.table.DefaultTableModel;
public class PopulateTableWorker
extends SwingWorker<DefaultTableModel, Object[]> {
private final DefaultTableModel model;
public PopulateTableWorker(DefaultTableModel model){
this.model = model;
}
@Override
protected DefaultTableModel doInBackground() throws Exception {
// While there are more rows
while(Math.random() < 0.5){
// Get the row from the slow source
Object[] row = {1, "Java"};
Thread.sleep(2000);
// Update the model with the new row
publish(row);
}
return model;
}
@Override
protected void process(List<Object[]> chunks){
for(Object[] row : chunks){
model.addRow(row);
}
}
}
Note that the table model interface does not support addition of new rows. Alternatively we can make use of the table model interface. The model must be able to add a new row when this is required as otherwise an exception may be thrown.
import java.util.List;
import javax.swing.SwingWorker;
import javax.swing.table.TableModel;
public class PopulateTableWorker
extends SwingWorker<TableModel, Object[]> {
private final TableModel model;
private int rowIndex = 0;
public PopulateTableWorker(TableModel model){
this.model = model;
}
@Override
protected TableModel doInBackground() throws Exception {
// While there are more rows
while(Math.random() < 0.5){
// Get the row from the slow source
Object[] row = {1, "Java"};
Thread.sleep(2000);
// Update the model with the new row
publish(row);
}
return model;
}
@Override
protected void process(List<Object[]> chunks){
for(Object[] row : chunks){
for(int columnIndex=0, size=row.length;
columnIndex<size;
columnIndex++){
model.setValueAt(row[columnIndex], rowIndex, columnIndex);
}
}
rowIndex++;
}
}
Back to our example, we can have an interface called Informable (or you can pick a name of your liking) with one method: messageChanged(String message), which will be invoked whenever some progress is made and published.
public interface Informable {
void messageChanged(String message);
}
The worker also requires an instance of the interface as it will be used to publish the results through.
import java.io.File;
import java.util.List;
import javax.swing.SwingWorker;
public class SearchForWordWorker
extends SwingWorker<Integer, String> {
private final String word;
private final File[] documents;
private final Informable informable;
public SearchForWordWorker(String word,
File[] documents,
Informable informable){
this.word = word;
this.documents = documents;
this.informable = informable;
}
@Override
protected Integer doInBackground() throws Exception {
int matches = 0;
for(int i=0, size=documents.length; i<size; i++){
// Update the status: the keep an eye on thing
publish("Searching file: "+documents[i]);
try {
// Do the search stuff
// Here you increment the variable matches
} finally {
// Close the current file
}
// update the progress
setProgress( (i+1) * 100 / size);
}
return matches;
}
@Override
protected void process(List<String> chunks){
for(String message : chunks){
informable.messageChanged(message);
}
}
}
The above worker can be easily plugged into the application as show in the following example. This application has three graphical components: a label acting as a title displaying the latest message published by the worker; a text area which displays all messages published by the worker; and a progress bar showing the progress made.
The label and text area are governed by Informable interface. The progress bar is governed by the worker's progress property.
import java.awt.*;
import java.beans.*;
import java.io.*;
import javax.swing.*;
public class Application extends JFrame {
// The UI Components
private JLabel label;
private JProgressBar progressBar;
private JTextArea textArea;
private void initComponents(){
// The interface will update the text of the UI components
Informable informable = new Informable(){
@Override
public void messageChanged(String message){
label.setText(message);
textArea.append(message + "\n");
}
};
// The UI components
label = new JLabel("");
add(label, BorderLayout.NORTH);
textArea = new JTextArea(5, 30);
add(new JScrollPane(textArea), BorderLayout.CENTER);
progressBar = new JProgressBar();
progressBar.setStringPainted(true);
add(progressBar, BorderLayout.SOUTH);
// The worker parameters
String word = "hello";
File[] documents = {new File("Application.java"),
new File("Informable.java"),
new File("SearchForWordWorker.java")};
// The worker
SearchForWordWorker worker =
new SearchForWordWorker(word, documents, informable){
// This method is invoked when the worker is finished
// its task
@Override
protected void done(){
try {
// Get the number of matches. Note that the
// method get will throw any exception thrown
// during the execution of the worker.
int matches = get();
label.setText("Found: "+matches);
textArea.append("Done\n");
textArea.append("Matches Found: "+matches+"\n");
progressBar.setVisible(false);
}catch(Exception e){
JOptionPane.showMessageDialog(Application.this,
"Error", "Search",
JOptionPane.ERROR_MESSAGE);
}
}
};
// A property listener used to update the progress bar
PropertyChangeListener listener =
new PropertyChangeListener(){
public void propertyChange(PropertyChangeEvent event) {
if ("progress".equals(event.getPropertyName())) {
progressBar.setValue( (Integer)event.getNewValue() );
}
}
};
worker.addPropertyChangeListener(listener);
// Start the worker. Note that control is
// returned immediately
worker.execute();
}
// The main method
public static void main(String[] args){
SwingUtilities.invokeLater(new Runnable(){
public void run(){
Application app = new Application();
app.initComponents();
app.setDefaultCloseOperation(EXIT_ON_CLOSE);
app.pack();
app.setVisible(true);
}
});
}
}
The above example builds the application and kicks off the worker. The worker updates the application through the Informable instance. While the worker is performing it task, the application can carry on doing other things (event listening and painting) without hanging.
Cancel the Worker
Can we cancel the task? Yes. The worker can be stopped or better cancelled. The worker provides a method called cancel which accepts a parameter of type boolean. This parameter determines whether or not the worker should be waked up should it be found sleeping.
import java.awt.*;
import java.awt.event.*;
import java.beans.*;
import java.io.*;
import javax.swing.*;
public class Application extends JFrame {
private JLabel label;
private JProgressBar progressBar;
private JTextArea textArea;
private JButton button;
private SearchForWordWorker worker;
private void initComponents(){
// The interface will update the text of the UI components
Informable informable = new Informable(){
@Override
public void messageChanged(String message){
label.setText(message);
textArea.append(message + "\n");
}
};
// The UI components
label = new JLabel("");
add(label, BorderLayout.NORTH);
textArea = new JTextArea(5, 30);
add(new JScrollPane(textArea), BorderLayout.CENTER);
// The cancel button
button = new JButton("STOP");
button.addActionListener(new ActionListener() {
public void actionPerformed(ActionEvent event) {
// Cancel the worker and wake it up should it be sleeping
worker.cancel(true);
}
});
add(button, BorderLayout.EAST);
progressBar = new JProgressBar();
progressBar.setStringPainted(true);
add(progressBar, BorderLayout.SOUTH);
// The worker parameters
String word = "hello";
File[] documents = {new File("Application.java"),
new File("Informable.java"),
new File("SearchForWordWorker.java")};
// The worker
worker = new SearchForWordWorker(word, documents, informable){
@Override
protected void done(){
try {
int matches = get();
label.setText("Found: "+matches);
textArea.append("Done\n");
textArea.append("Matches Found: "+matches+"\n");
progressBar.setVisible(false);
}catch(Exception e){
JOptionPane.showMessageDialog(Application.this,
"Error", "Search",
JOptionPane.ERROR_MESSAGE);
}
}
};
// A property listener used to update the progress bar
PropertyChangeListener listener =
new PropertyChangeListener(){
public void propertyChange(PropertyChangeEvent event) {
if ("progress".equals(event.getPropertyName())) {
progressBar.setValue( (Integer)event.getNewValue() );
}
}
};
worker.addPropertyChangeListener(listener);
// Start the worker. Note that control is
// returned immediately
worker.execute();
}
public static void main(String[] args){
SwingUtilities.invokeLater(new Runnable(){
public void run(){
Application app = new Application();
app.initComponents();
app.setDefaultCloseOperation(EXIT_ON_CLOSE);
app.pack();
app.setVisible(true);
}
});
}
}
This will cause the worker's get method to throw the exception CancellationException to indicate that the worker was forced cancellation.
Conclusion
One thing to take from this article is: when possible do not refer to UI components directly from the worker. The worker is better viewed as the subject of the observer pattern. Provide an interface which the worker will use to communicate with its owner (application).
