The method setBounds() of of the class component does not execute as expected.
Tests show that a frame gets a setBounds() call with the correct boundaries.
The call gets ignored by the peer. Additional call to setBounds() bring the
peer completely out of sync.

An inacceptable workaround is to set the JFRame in a reshape to visible an to call
super.reshape() later on. This work around hiwever does not work on all platforms.

The bug is based on a race condition. It almost never occurs as long as localhost aka local display is being used. It occures quite often by using X11
remote displays.

The result of the bug is a screen with zero size. It is almost impossible to
detect the frame on the screen. It is very difficult to find the right pixel to
expand it (after having been found).


###@###.### 2001-08-20
The bug could not be reporduced after all available CDE,Motif and X11 scripts
had been applied on the X11 Server as well on the X11 Client side Solaris systems.

The bug has originally been filed against a Hewlett Packard X11 Server and a Solaris client.
The customer has been asked to file the problem at Hewlett Packard for this reason.

###@###.### 2001-08-20