Bug ID: JDK-4142012 1.2 Beta 4: Multiple AWT event queues not supported

JDK-4142012 : 1.2 Beta 4: Multiple AWT event queues not supported

Type: Enhancement
Component: client-libs
Sub-Component: java.awt
Affected Version: 1.2.0

Priority: P3
Status: Closed
Resolution: Fixed
OS: solaris_2.5
CPU: generic

Submitted: 1998-05-26
Updated: 1999-01-15
Resolved: 1999-01-15

Versions (Unresolved/Resolved/Fixed)

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.

Other
1.2.0 1.2fcsFixed

Related Reports

Relates :	JDK-4142011 - 1.2 Beta 4: Multiple AppContext objects not supported
Relates :	JDK-4152133 - Win32 peers should never call user code on the AWT-Windows thread
Relates :	JDK-4156853 - appletviewer should allow applets access to their EventQueue objects
Relates :	JDK-4159054 - sun.awt.AppContext needs a dispose()
Relates :	JDK-4152184 - Motif peers should never call user code on the AWT-Motif thread

Description

Multiple per-applet event queues should be implemented by the AWT.

This RFE can't be addressed until multiple AppContext objects are possible,
however (see bug ID 4142011).

Comments

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic FIXED IN: 1.2fcs INTEGRATED IN: 1.2fcs

14-06-2004

EVALUATION After addressing Bug ID 4124011 (multiple AppContext support), I made a new EventQueue be created whenever an AppContext is created (in SunToolkit.createNewAppContext()), stored the EventQueue in the AppContext's hash table, and made the peers keep track of their AppContext so their events get posted to the right EventQueue. This works great, but anywhere the AWT-Windows/AWT-Motif threads call client code, it breaks the model. Thus, bug IDs 4152133 and 4152184 must be fixed! fred.ecks@Eng 1998-06-25

25-06-1998