When you place beans in the Visual Composition Editor:
It is not good interface design for one bean to overlay another bean. Completely or partially overlaying a bean can result in focus problems, causing users to see but be unable to select the bean.
By embedding composite beans into other composites, you minimize the confusing spider effect of connection lines. For example, you can create a composite bean that consists of a panel on which you have placed buttons and check boxes, and make connections. When you embed this bean in your main interface, you cannot see the connection lines. You place and work with the composite as one bean--not as a panel and separate buttons and check boxes.
If you need to edit the composite or its internal connections, you simply select Open from the pop-up and the Visual Composition Editor for the composite appears, as described in Editing Beans within a Composite Bean.
Visual Composition Editor Overview
Visual Programming Fundamentals
How Classes and Beans Are Related
Visual, Nonvisual, and Composite Beans
Working with Beans Visually
Composing Beans Visually
Adding the IBM Java Examples project
Visual Composition Editor
The Menu Bar in Visual Composition
Properties
Pop-Up Menus for the Visual Composition Editor