JDK-6493680 : SwingWorker notifications might be out of order.
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 6
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2006-11-14
  • Updated: 2011-03-08
  • Resolved: 2011-03-08
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7
6u1Fixed 7 b07Fixed
Description
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 "progress"
property change after done method is invoked for example.

Comments
EVALUATION 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.
14-11-2006