When a JButton is placed inside a JFrame, calling setCursor in response to an
action event generated by the JButton results in incorrect behavior. In the
application below, clicking the JButton should cause the cursor to be set to the
Wait Cursor. Instead, the Wait Cursor appears briefly before being replaced by the Default Cursor.

This bug presents a particular problem for client applications that set the cursor to Wait Cursor while performing an RMI call. If the cursor is not set properly, the user will often attempt to resubmit the data, clicking the mouse or hitting the return key multiple times, causing the client-side application to hang. The client must be killed, which interrupts RMI on the server. When interrupted, RMI may fail to clean up nicely, and it then needs to be restarted on the server before the client-side application can be restarted.

The JDK used is 1.1.6, the Swing version is 1.0.2

------------------------------ TestCursor.java --------------------------------

import java.awt.*;
import java.awt.event.*;
import com.sun.java.swing.*;


public class TestCursor extends JFrame {

    public TestCursor() {

    super("TestCursor");
    setLocation(200,200);
    setSize(200,200);
        addWindowListener(new WindowAdapter() {
            public void windowClosing(WindowEvent e) {
                System.exit(0);
            }
        });

    JButton okButton = new JButton("OK");
    okButton.addActionListener(new ActionListener() {
        public void actionPerformed(ActionEvent e) {
        setCursor(new Cursor(WAIT_CURSOR));
        }
    });

    getContentPane().add(okButton);
    }

    public static void main(String args[]) {
    TestCursor test = new TestCursor();
    test.show();
    }
}