Oracle® Application Server Portal User's Guide
10g Release 2 (10.1.4) B13809-04 |
|
Previous |
Next |
This appendix summarizes the rules that apply to the naming of objects in OracleAS Portal. Unless otherwise indicated, names and display names are not case sensitive. In other words, in most cases APP is the same as app.
Table D-1 Object Naming Rules in OracleAS Portal
Object | Name | Display Name |
---|---|---|
|
|
|
|
|
|
|
With HTML templates, the Template Name doubles as a Name and a Display Name |
|
Items and Portlets |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Regions do not have a Name field |
|
|
|
|
|
|
|
Notes
In OracleAS Portal, Name uniqueness is preserved automatically by the addition of a value.
If the Shared Objects page group contains an object that uses the same name as an object that you move to the Shared Objects page group, OracleAS Portal appends a value to the Name (internal name) of the moved object. This is to maintain name uniqueness within the page group.
For example, imagine that the Shared Objects page group contains a category named sample_category. Another page group, Division, contains a category that is also named sample_category. You move sample_category from the Division page group to the Shared Objects page group. OracleAS Portal appends a value to the moved category, such as sample_category_AABkUWAAJAABpiAAC. You can revise the internal name, but you cannot give it the same Name as any other object in the Shared Objects page group.
The same rule applies when you try to create any object with a Display Name that duplicates another object's Name. OracleAS Portal uses an object's Display Name to create the object's (internal) Name. If you enter the Display Name red for an object, and another object already uses the name red. The first object's Display Name will be red, but its Name will have a value appended to it to make it unique, for example, red1.