Relationship Between Templates and Definitions Serving Web Pages

2-6 Oracle Fusion Middleware Technical Reference Guide for Site Studio xWebsiteObjectType Matches `Native Document`]] dataProperty complexProperty dataProperty name=defaultmetadata [CDATA[]] dataProperty complexProperty regionDefinition

2.3.3 Element Definitions

Each element definition, just as with other site assets, is a simple XML file. The static list element definition files will have more code in the XML because it must list each element definition used within the static list. Custom elements will not be any more complex than other element definitions, because custom elements simply load a separate form in HTML. Example Code The code for an element definition can vary widely depending on the type of element. All elements will contain a complexProperty name=flags section to describe the flags and their state. The flags used by an element through the element definition depend on the element. Because of the variations in code for the element definitions, none are represented here. To see the differences in the code, open the element definitions in Designer.

2.4 Relationship Between Templates and Definitions

The idea is to make this section a technical description of the interactions between the template and the definition to control page layout and reusability. All data must be tagged with a region definition. That is how it is placed with the appropriate definition and template combination.

2.5 Serving Web Pages

Since each asset is stored individually, the page is combined on the server before it is served to the client. The assets used to construct are selected based on the references in each other asset, as previously described. The general process of events in creating the page happens in this manner after the request is made: 1. The page template is loaded based on the requested URL. A specific page request will load the page template associated with that page, and a request for a folder or the root will load the page template named in the project file. That templates name is editable through the properties pane in Designer. 2. All assets not listed in a placeholder are loaded. 3. As the assets outside of the placeholder are loaded, the Idoc script is executed and the placeholder is filled, starting with the evaluation of the placeholder definition. The specific placeholder definition for the page is loaded in this order: ■ The placeholder definition explicitly named in the wcmPlaceholder tag. Site Asset Relationships and File Structure 2-7 ■ If no placeholder definition is specifically listed in the tag, the definition listed in the section properties based on the URL is used. ■ If the section properties lists no placeholder definition, then the definition used in the global definition mappings is used. ■ If there is no placeholder definition listed in the global definition mappings, then the placeholder listed in the web site properties in the properties pane is used. 4. The data file used is based on the value listed in the Primary or Secondary Page Params in the section properties. The exception is when the data file to use is listed explicitly in the wcmPlaceholder tag.

5. The xRegionDefinition metadata field for the data file lists which region

definition to use. Again, this is when a region definition is not explicitly listed in the wcmPlaceholder tag. 6. The region template and element definitions used are determined from the settings in the region definition, unless a different region template is stated in the wcmPlaceholder tag. 7. Once all elements are collected, the page is asembled and served. For more information on using wcmPlaceholder, see Section 9.2, wcmPlaceholder.

2.6 Conversions Definitions