Database Tables

If gears you are developing require database tables, it is important to take steps to prevent the possibility of different gears using the same table names. We recommend using prefixes in the table names to indicate which gear will be accessing these tables. Doing so will help database administrators manage the portal data.

Java Class Instance Naming

With a standalone Java application, Java class instance naming conflicts are not a problem. However, with a portal the Page, Session, and Application Contexts will be used by several different gears. Consequently, it is important to keep this in mind when naming class instances for storage in the contexts. Using a prefix that uniquely identifies the gear that is using a class instance is a good way to avoid class instance naming conflicts.