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) 
======================================================================

N/A

This sounds like a result of 4030718.  We should document this change more 
thoroughly.  I attached the draft document   xxxxx@xxxxx   wrote.  
  xxxxx@xxxxx   2002-10-21

As a partial fix to this problem, I have edited Danila's document and placed it into the mantis release at awt/doc-files/AWTThreadIssues.html.  This will then be references from various places in the javadoc and the tutorial.  I have also drafted some text to be added to the 1.4.0 incompatibility page.
  xxxxx@xxxxx   2002-12-11

The information has been added to the compatibility page as well as to AWT in Window.java and EventQueue.java.  It still needs to be added to the Swing files and the tutorial.
  xxxxx@xxxxx   2002-12-15

Fixed for mantis.  (CCC request was filed.)
  xxxxx@xxxxx   2003-01-28