Defining the Element Content 
Defining the Element Content
In general, BSP elements have a particular content. This means that the resulting tags consist of a start and an end tag, and between these two there are either further (embedded) tags, script elements, or even simply just text. By selecting the option for the Element Content in the attribute display of the BSP element, you can define whether content should be embedded in the element or not, and – if so – which content.
The display options comprise the following:
|
Empty |
|
|
You select this option if the BSP element is not to have any content.
Example: Input field from the BSP extension HTMLB<ui:inputField id="myID" value="" /> or <ui:inputField id="myID" value="" > </ui:inputField > |
|
|
Solely BSP Elements |
|
|
By selecting this option, you define that the BSP element is only to contain further BSP elements. Any existing HTML part will be ignored by the runtime environment. This reduction enables you to achieve performance optimization during runtime.
Example: Tree element from HTMLB<ui:tree id="myTREE"> <ui:treeNode id="ROOT" text="Root node"> <ui:treeNode id="N1" text="Node 1"/> <ui:treeNode id="N2" text="Node 2"/> </ui:treeNode> </ui:tree> |
|
|
BSP Elements and Static HTML |
|
|
This element can include both further BSP elements as well as any HTML part.
Example: Form element from HTMLB<ui:form id="myFormID" method="POST"> <ui:inputField id="myID" value="" size="24"/> <br> <br> Some Text ... <a HREF="" ...> ...</a> </ui:form> |
|
|
Element Interprets the Content Itself |
|
|
With this selection, you define that the content of the element is to be passed on unchanged, without previous parsing, to the element handler class. This is appropriate whenever an interpretation of the element content is not required by the runtime environment.
Example: The BSP element executes an SQL statement that must be specified in the element content.<sql:selectStatement> SELECT * from SFLIGHT into table myFlights </sql:selectStatement > |
|
