Components that override getPreferredSize and getMinimumSize layout incorrectly using the BorderLayout. It's as if BorderLayout forgot to call the new getPreferredSize and defaults to the deprecated preferredSize.

On delenn.eng running CDE (or kosh.eng running OpenWin), I minimized my environment variables:

% printenv
CLASSPATH=.:/usr/local/java/jdk1.1.bak/solaris/lib
DISPLAY=:0.0
JAVA_HOME=/usr/local/java/jdk1.1.bak/solaris/
LANG=C
PATH=/usr/local/java/jdk1.1.bak/solaris/bin:/usr/ccs/bin:/usr/bin:/usr/sbin:/usr/lib:/usr/ucb:/usr/local/bin:.
SHELL=/java/dist/exe/tcsh
USER=brie
WINDOWID=142606349

Then I invoked /home/brie/workspaces/awt11-test/layout/BorderBug3:

% cd ~brie/workspaces/awt11-test/layout
% $JAVA_HOME/bin/java BorderBug3

The desired visual result would be 2 equally sized rectangles with 150 pixels of background vertically between them. The observed visual result is one large rectangle obscuring the majority of the second, with no background showing. This observation indicates that the preferredSize and minimumSize methods are called even when the getPreferredSize and getMinimumSize methods are overridden.

This is further confirmed by the addition of:

new Exception().printStackTrace()

in each of the depreciated methods.