In general, name builders in models using the same conventions as Java variables.
(Initial lowercase character, then an uppercase character for the first letter of each word.) For example:
Sometimes the initial lowercase rule should not be followed. For example, the Name
input of the Portlet Adapter builder is used as the portlet name in the portal (not for generated web application objects), so using initial uppercase letters for this builder call name makes more sense.
input for control builders (such as Button or Link builders) is generally best left blank. When this input is blank, the control builder automatically displays the name of the tag on which it is located.
Duplicate name error
If you create an LJO with the same name as an existing variable or LJO, WebSphere® Portlet Factory throws an exception (duplicate name error). Duplicate names can cause runtime issues that are difficult to diagnose and fix. This error avoids runtime collisions that could possibly cause obscure errors when the application runs. You can see this error at either design time or runtime. The error occurs in one of the following cases.
- If you incorrectly name an LJO directly with the Linked Java Object builder.
- If you incorrectly name an LJO indirectly through the name of a builder call that itself creates an LJO with that builder name.
To avoid this error, change the name of one of the builder calls that creates the duplicate name error.
Parent topic: About using the builder call editor