Java Solaris Communities Sun Store Join SDN My Profile Why Join?
 
Bug Database
Bug Detail
Quick Lists
Top 25 Bugs
Top 25 RFE's
Recently Closed Bugs
Printable Page Printable Page


Bug Database
Bug ID: 4639354
Votes 15
Synopsis AWT headless toolkit should document how to lay out and realise Components
Category java:classes_awt
Reported Against 1.4
Release Fixed
State 6-Fix Understood, request for enhancement
Priority: 4-Low
Related Bugs
Submit Date 18-FEB-2002
Description
The new AWT headless toolkit in JDK 1.4 allows developers to create instances of
lightweight components. (ie components with a lightweight peer)
Normally to realise (request peer creation) and layout these components
they are added to a top-level container such as a Window or Frame or (in the
case of Swing components, the JFrame subclass of Frame). However each of
these top-level components cannot be created in a headless toolkit.

In a headful toolkit a developer who wishes to create but not display these
componnets could create a Frame and call Frame.pack(). Clearly this is not
an option in the headles toolkit. The remaining options for developers in
a headless toolkit are to craft code which replicates the effect of pack(),
or to call Container.addNotify(). The former option may be fragile and
difficult without knowledge of the inner workings of the toolkit, the latter
is not strictly meant to be called by developers.

Since the headless toolkit was designed to allow creation of lightweight
Component hierarchies, it is important to show how this can be done in
a reliable, supported, cross platform way.

This is needed (for example) to be able to print Components in a headless
environment.
Work Around
N/A
Evaluation
This is a duplicate request of 4356383, which was closed out by the Swing team.  Reassigning to them for advice.  Likely they will want me to help write an article for the Swing Connection on this subject.
  xxxxx@xxxxx   2002-05-23
Comments
  
  Include a link with my name & email   

Submitted On 05-MAR-2006
cowwoc
Is there an update on this issue?



PLEASE NOTE: JDK6 is formerly known as Project Mustang