I would not use a null layout manager. This only works on screens that only are displayed on one platform AND are never minimized, maximized or moved (as when these events occur, the explict positioning is lost and the system will revert to a flow layout)
For the purpose of the license(s) included with this product, the redistributables for the JavaBeans Component Library (JBCL) is defined as the jbcl.jar and jbcl-awt.jar files in the /jbuilder2005/redist directory, and/or the individual files in those archives.
To the extent that you are allowed to redistribute redistributables under the terms of your license, you may redistribute these classes in any of the following formats subject to the restrictions in the license agreement:
and from the JBuilder online help:
XYLayout is a JBuilder custom layout manager. XYLayout puts components in a container at specific x,y coordinates relative to the upper left corner of the container. Regardless of the type of display, the container will always retain the relative x,y positions of components. However, when you resize a container with an XYLayout, the components do not reposition or resize.
XYLayout is very convenient for prototyping design work. When you design more complicated user interfaces with multiple, nested panels, XYLayout can be used for the initial layout of the panels and components, after which you can choose from one of the standard layouts for the final design.
Note: To ensure your layout will be nicely laid out on other displays, don't leave any containers in XYLayout in your final design
So it's there almost purely for prototyping and internal use by the IDE.
Check if the application really uses it. If not, just remove the import (a common mistake, leaving imports in place).
If it is, and you don't have a JBuilder version that allows redistribution of the JBCL jars or you don't want to leave it in, redesign the user interface to use other layout managers (which is what Borland themselves advise you to do).
The null layout is not as good as it appears at first sight because it fixes the locations of the objects; changing the size or proportions of the JFrame may cause them to disappear or may show empty space on part of your window.
Try GridLayout before using GridBag, because it is easier to understand. Look at Cay Horstmann's website, where there is a class called "GBC" which makes handling GridBag quicker and easier.