Child Elements

The PAGE element can contain child elements as follows:

Table 1. Child Elements of the PAGE Element

Element Name

Cardinality / Description

INCLUDE

0..1. This element can be used before any other child element of a PAGE element.

PAGE_TITLE

0..1

DESCRIPTION

0..1

SHORTCUT_TITLE

0..1

SERVER_INTERFACE

0..n. Multiple SERVER_INTERFACE elements are supported, however it is recommended that only one SERVER_INTERFACE with the PHASE attribute set to ACTION is defined per PAGE element. See SERVER INTERFACE for more information.

INFORMATIONAL

0..1

MENU

0..2. The page can contain one optional static and one optional dynamic menu as well as append extra items to the navigation menu.

ACTION_SET

0..1. In this context, the action set defines the set of action controls that will appear around the page's main content area.

PAGE_PARAMETER

0..n

CONNECT

0..n. In this context, the connections can copy values directly from the properties of source server interfaces to properties of the target server interfaces. Each CONNECT element should contain both a SOURCE and a TARGET element.

JSP_SCRIPTLET

0..n. JSP_SCRIPTLET, CLUSTER and LIST can be intermingled freely and the order in UIM will be preserved in the generated page.

CLUSTER

0..n. JSP_SCRIPTLET, CLUSTER and LIST can be intermingled freely and the order in UIM will be preserved in the generated page.

LIST

0..n. JSP_SCRIPTLET, CLUSTER and LIST can be intermingled freely and the order in UIM will be preserved in the generated page.

SCRIPT

0..n. A script associated with the PAGE that will be activated in response to the specified event. See SCRIPT for more details.

Where a page is configured to contain a large number of scrollable list and cluster elements (approximately 15), it may cause JSP compile issues in Weblogic. This is due to a Weblogic system limitation in how big a page can be rendered at run time. To overcome this restriction, arrange the display of the required scrollable lists and clusters over a number of pages.