JDK-4670707 : Need for daemon property on AWT components
  • Type: Enhancement
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 1.4.0
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: generic
  • CPU: generic
  • Submitted: 2002-04-18
  • Updated: 2002-04-19
Related Reports
Relates :  
Relates :  
Relates :  

Name: dsR10078			Date: 04/18/2002

The solution for the bug 4030718 requires that any displayable AWT or
Swing component must be made undisplayable before AWT can shutdown

However in some cases there is a need to specify that certain AWT
components should not block AWT shutdown even if they are
displayable. Such a need has been expressed by the Input Method team.

"Java input methods are input methods written by third party software 
vendors, which have nothing to do with the running Java
application/applet. So in a sense, Java input methods are regarded as
system side modules and I think the auto shut down should run even if
peers for input method windows still exist."

The reasonable solution seems to add a 'daemon' property to a Window,
so that when this property is set on a Window, it won't block AWT
shutdown even if it is displayable. This way, input method vendors
would be able to set this property on the input method windows they
display and wouldn't have to dispose them explicitly.

This RFE is needed to provide a complete solution for 4515058.

###@###.### 2002-04-18

WORK AROUND Name: dsR10078 Date: 04/18/2002 ======================================================================