SwingWorker notifications might be out of order.

After the fix for 6449017 [SwingWorker performance is sluggish] some
of the SwingWorker notifications come by a different route than
before. While the spec does not provide any guarantees about the order
asynchronous notifications are to be handled the usual expectation is
notification which is sent later is to be handled later. After that
fix it is not the case any more. SwingWorker might receive " customer "
property change after done method is invoked for example.
Posted Date : 2006-11-14 20:27:28.0

N/A

I suggest to publish all the SwingWorker notifications using the new mechanism introduced in the fix for  6449017 [SwingWorker performance is sluggish]. This will guarantee the expected order.
Posted Date : 2006-11-14 20:30:19.0

I'm still getting this but -- a progress event sometimes arrives after the done event to my propertyChangeListeners on the SwingWorker.   Progress is reported in doInBackground(), done events should only be triggered after that method finishes, so they shouldn't arrive out of order to the listener.  I'm using:

 Java(TM) SE Runtime Environment (build 1.6.0_10-beta-b25)
Java HotSpot(TM) Client VM (build 11.0-b12, mixed mode, sharing)

Christopher