Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2046671 | 5.0 | Sharon Zakhour | P4 | Resolved | Fixed | b03 |
Name: bsC130419 Date: 08/23/2001
1.4.0beta documentation
The method description of java.awt.Window.dispose() doesn't mention that
calling dispose() can cause the JVM to exit, and doesn't specify the
conditions under which that happens.
- It should describe (or refer the reader to some other description of)
how the AWT keeps track of windows and exists when the last window is
disposed.
(Consider my documentation-reading scenario: The behavior has changed
from AWT behavior in the past. I notice it when I call dispose(), so
I look at that method's documentation. It mentions nothing, so I travsere
up, looking in Window's class description. It mentions nothing, so I
traverse up to package java.awt, but its description mentions nothing.
The information, or a pointer to it, should be accessible close to that
traversal chain. Otherwise, how will readers find it in a reasonable
amount of time?)
- It and/or the documentation of Frame.getFrames() should specify whether
disposed frames are still listed in getFrames' result.
DSB
(Review ID: 130574)
======================================================================
- backported by
-
JDK-2046671 Window.dispose() doesn't document JVM-exiting behavior
-
- Resolved
-
- relates to
-
JDK-4030718 A program which calls Toolkit.getDefaultToolkit() won't terminate.
-
- Resolved
-