Oracle JHeadstart Developer's Guide - Downloads - Oracle

3.2.3. Renaming Entity Objects and Associations
• We first rename the entities and associations and the new names will be used
when we create view objects and view links.
• A default application module typically contains many (nested) view object
usages that you do not need in your application. You should set up your
application module data model based on the layout of the pages you will create
to meet the functional requirements of your application.
We recommend renaming entity objects and associations to comply with the naming
standards you have set up for your project (see chapter 2).
Renaming associations and the association accessors is important for the following
reasons:
• By default, associations are named after the foreign key constraint suffixed with
“FkAssoc”. Foreign key names are often not very meaningful, so if you have
many associations, they are easier to manage with meaningful names.
• The accessor properties of an association determine the accessor method names
generated into the entity objects to traverse entity object associations, something
you will often do when coding business rules in your entity objects. Logical
accessor methods make it easier to code this logic.
• The view links that are created when you create default view objects for your
entity objects are named after the underlying associations, saving you an
additional renaming of the view links (although you typically will remove the
“Link” suffix added to the view link name).
For example, when you create entity objects for the EMPLOYEES and DEPARTMENTS
tables in the HR schema of the Oracle database, an association named DeptMgrFkAssoc
is created, with association properties named “Employees” and “Departments”. We
recommend renaming the association to something like
“EmployeeManagesDepartments”, and the association properties to “Manager” and
“DepartmentsManaged”.
3 - 6 Creating Business Components JHeadstart Developer's Guide