Class EventQueue

java.lang.Object
vaadinx.awt.EventQueue

public class EventQueue extends Object
Emulator for EventQueue. Three EDT primitives — invokeLater(Runnable), invokeAndWait(Runnable), isDispatchThread() — delegate to SwingUtilities and bottom out in UI.getCurrent() != null (the Vaadin UI-thread proxy); getMostRecentEventTime() returns System.currentTimeMillis(). The remainder of the JDK surface (instance dispatch machinery, postEvent, peekEvent, getNextEvent, dispatchEvent, getCurrentEvent, push / pop, createSecondaryLoop) is present so migrated code compiles, but each method WARNs via EHelper.onUnimplemented(String, String, Object...) and returns a safe default — no AWT EventQueue dispatch thread exists server-side, so the dispatch contract can't be honoured. This matches R_match_swing_errors / D_never_fail_on_gaps: log the gap, never crash the host app.

Why ported despite not being Component-shaped. The JDK EventQueue bottoms out in an AWT EventQueue dispatch thread that doesn't exist server-side; EventQueue.invokeLater(...) against the JDK class would silently queue the runnable and never run it. The porting rule is "port what would silently fail server-side; leave what works unchanged on the JDK" — EventQueue's static EDT methods fall on the port side, and once the class is present the rest of its API surface is added as WARN-stubs to avoid compile errors on incidental references.