Introduction to Swing Borders

When you lay out a Swing interface, components often end up crowded against the edges of their containers. A panel full of buttons can have its buttons touching the panel's boundary, and a text label can sit flush against the edge of its own area. The fix is not to rearrange the components themselves. Swing gives you a separate tool for the space around the outside of a component, and one of the most practical of those tools is the empty border.

The word empty is literal. The border does not paint a line, a bevel, or a pattern. It only reserves room. Because nothing is drawn in that reserved room, whatever background color the component has will fill the space. The key idea to hold onto is this: the border adds space, and the component's own background shows through that space.

The method takes four parameters, always given in the same order: top, left, bottom, right. Each parameter is an integer giving the width of the border along that edge of the component. Because the order is fixed, the first number always controls the top edge, the second the left edge, the third the bottom edge, and the fourth the right edge. Mixing up that order is the most common reason a border looks wrong.

Follow the state of a JPanel that holds other components. Without a border, the components inside the panel can sit right at the panel's edge. Adding an empty border moves the usable area inward, because the reserved space now sits between the panel's outer boundary and the components placed inside it. The panel's background color is still present across the whole panel, including the reserved space.

The source gives a second common use: a JLabel. Without an empty border, a label has no space between its text and the edge of the label. The text can touch the label's boundary. Adding an empty border creates that space, so the text no longer touches the edge of the label's area.

Suppose you have already learned how to leave gaps between the components inside a container. Gaps like these separate components from one another. A different question comes up quickly: how do you draw a visible line around the outside edge of a container itself? The source makes a direct point here. Layout managers do not handle the border around the outside of a container. Arranging components and spacing them apart is the layout manager's job, but drawing a border around the outside is a separate concern, and Swing solves it with a different mechanism.

That mechanism is the border object. In Swing, a border is not a setting you type in as a plain number or a word. Borders are represented by objects that you can create, hold in a variable, and hand to a component. A border is something you build first and then attach. Because the border is an object with its own appearance, it can do more than reserve blank space. It can draw something visible, such as a line.

The reach of this idea is broad. A Border object can be added to any JComponent, not just to containers. A label, a button, or a panel can all receive a border in the same way, because the mechanism belongs to JComponent as a general capability.

Because borders are objects, you need a way to obtain one. The class javax.swing.BorderFactory provides that. It contains a large number of static methods, and each one returns a border object. Since the methods are static, you call them on the class itself rather than on an instance you have made. Each call hands back a new border object that you can store and use.

The source's example is BorderFactory.createLineBorder(Color.BLACK), which returns a one-pixel wide black line. Read the call as a request: ask the factory for a line-style border, and specify the color as black. The call's result is a border object. The call itself does not draw anything on the screen yet. It produces an object that represents a border, and attaching that object to a component is a separate step.

Once you have a border object, you still have to connect it to the component it should surround. A border is attached to a JComponent by calling its setBorder() method with the border object as the argument. The component is the object that receives the call, and the border object is the argument you pass in.

Read the pipeline left to right. The factory call produces a border object, that object is passed to setBorder(), and the component receives it. Creating the border and attaching it are two separate actions, each with its own part of the code. Trace one border from start to finish: start with the request, follow the object it produces, and end with the component that keeps it.