# Understanding Default Business Components

After creating a business components project, you have business components in your package, arranged in alphabetical order. For example:

Each table you selected in the wizard produced one entity object of the same name. Each entity object has a corresponding view object of the same name, but with the suffix "View." Where there was a foreign key to another table, an association and view link were created. The names were based on the database constraint names, with the suffix "Assoc" or "Link."

The default application module contains each view object and view link. This is similar to how a Java Frame can contain instances of components, such as buttons and text fields. A default application module is named the same as the package, but with the suffix "Module."

Business components are defined in Java files and XML files, which you can see by expanding the component's node:

Each default entity object, view object, and application module is defined in a Java file, which you can customize. In addition, each business component is defined in an XML file, which allows you to modify the application's behavior without recompiling Java code. If you look at one of the Java or XML files, you will see that each entity and view object has attributes corresponding to each column in the table.

Generating a default business components project provides a big head start in your development effort. Afterwards, you can customize the business components and add new business components to complete the business logic tier of your application. In addition, Business Components for Java lets you generate default JSP and DAC clients through JDeveloper wizards.