Home >	Contents >	Index >
Template Tag TOC  |   Alpha TOC  |   Tag Family TOC  |   Purpose TOC  |   Annotated TOC  |   Index

RENDER.CALLTEMPLATE

Invokes a Template, as either a pagelet or an element, for the purpose of rendering an asset.

Syntax

<RENDER.CALLTEMPLATE
        SITE="site name"
        SLOTNAME="name of slot"
        TID="caller Template or CSElement id"
       [d="Device Group Suffix"]
       [resolvetemplatefordevice="A boolean value indicating whether parameter 'd' should be ignored or not."]
       [TTYPE="caller Template or CSElement"]
       [C="asset type"]
       [CID="asset id"]
       [TNAME="target Template or CSElement name"]
       [CONTEXT="context override"]
       [STYLE="pagelet or element"]
       [VARIANT="template variant name"]
       [PACKEDARGS="packed arguments"]>
</RENDER.CALLTEMPLATE>

Attributes

site (required)

The name of the site containing the Template to be invoked.

slotname (required)

This attribute defines an identifier for the "slot" that is being filled with the called template. It should be reasonably easy to understand for humans and should be unique across all templates. Future versions of Sites will make extensive use of the slotname attribute.

tid (required)

The id of the template in which this tag is located. If this tag is located in a CSElement, then the value of this attribute should be the id of the CSElement, and ttype should be set to CSElement.

d (optional)

Device Group Suffix(a string that is common suffix of all the templates written for current device group). For example, if d ='Touch' and parameter tname = 'HomeLayout', the tag will try to find a template with name tname_d i.e. HomeLayout_Touch. If it exists, the tag will call this template, otherwise will simply call the template 'HomeLayout' i.e. actual tname provided.

resolvetemplatefordevice (optional)

true|false. Default is true. If 'false' is provided explicitly, the tag will ignore the parameter 'd' and will not try to re-direct to device group specific template.

ttype (optional)

This attribute identifies whether the code that contains this tag is a Template or a CSElement. The default value is Template, and CSElement is the other legal value. See tid.

c (optional, required for explicit mode)

The asset type to be rendered by the called Template. The value of this attribute will be passed to the called code. If c, cid, and tname are set, then context data is ignored.

cid (optional, required for explicit mode)

The id of the asset to be rendered by the called Template. The value of this attribute will be passed to the called code. This is required if c is set.

tname (optional, required for explicit mode)

The name of the Template to be called. This is required if c and cid are set. If these three attributes are not set, the called template will be determined by looking at context data. If tname refers to a typeless template, prefix the template name with '/' (/templatename).

context (optional, required for context mode)

This attributes contains a context override parameter. If c, cid, and tname are not specified, then this attribute value will be examined to determine which template to call and which asset to render using the specified template. If this value is not specified, then an ICS variable of the same name will be examined for the same purpose. If no context value can be located, then the slot will be not be populated, and this tag will do nothing. Future versions of Sites will provide an interface that allows the context data to be set automatically. Manually overriding this value should be considered an advanced technique.

style (optional)

Flag that indicates that the called Template should be called as an element or as a pagelet, and if it is to be called as a pagelet, should it be embedded in the parent for Satellite Server or should it be an independent pagelet. The default value is pagelet. Setting this attribute value to element will result in the template being called as an element. This is useful if a nested pagelet is not necessary or desireable (i.e. would be overkill) for the target Template. When the style is element, the scope of the called element is local: only variables specified as arguments and attributes will be accessible to the called element, and variable values in the caller will not be affected. When the style is set to embedded, the nested template is invoked as a pagelet without using Satellite Server. This causes the pagelet to be independently rendered (and possibly cached) by Sites but the result of the pagelet is embedded in the caller, just as if it had been called as an element. Satellite Server does not see embedded pagelets as separate from their caller; they are simply part of the output of the caller. Note that if this is set to element or embedded, then the invoked Template will be embedded in the caller, and this can have performance, dependency, and caching implications, which can be good or bad depending on your code).

variant (optional)

This attribute specifies the name of the Template variant to render. Template variants enable multiple code implementations of a Template (for example, WEP vs XHTML). Future versions of Sites may implement this feature; as of the current release it is not yet supported.

packedargs (optional)

This attribute contains a series of arguments (name-value pairs) URL-encoded as a string.

Description

This tag is the preferred method for invoking a template. It effectively replaces RENDER.SATELLITEPAGE, RENDER.CONTENTSERVER, and RENDER.CALLELEMENT in most (but certainly not all) cases. It causes a specific asset to be rendered by a specific template. The template can be rendered either as an inline element or as a nested pagelet (see style, above).

Instances of this tag must contain information about who the caller is in order to operate correctly. The caller must be either another Template or a CSElement. This tag will not operate correctly without valid information about the caller. (see tid & ttype above).

RENDER.CALLTEMPLATE operates in two modes: explicit mode and context mode.

In explicit mode, c, cid, and tname are explicitly specified as attributes to the tag. In essence, the asset identified by c and cid will be rendered by the template corresponding to the template named tname. If tname starts with "/" then the typeless template corresponding to tname will be called. Otherwise, the template corresponding to the specified tname and asset type ("c") will be called. Explicit mode is the only mode that is currently supported.

In context mode, the context attribute (which defaults to an ICS variable of the same name if not present) will be examined to determine the template and asset to be rendered. Context mode support is not currently enabled in the Sites interface, however future versions may include it.

Error Numbers

The possible values of errno include:

Example

The following example is in JSP, but the XML syntax is analogous. The following example, taken from the FirstSite Mark II Layout template, calls a template to render the html head tag. This tag displays the html title tag containing the description of the asset being rendered.

In this tag, most of the attribute values are set from other variables in the variable space, either because they have been passed in, or because they have been explicitly looked up.

The following table describes the origin of the ICS variables referenced below.

<render:calltemplate
        site='<%=ics.GetVar("site")%>'
        slotname="Head" 
        tid='<%=ics.GetVar("tid")%>' 
        c='<%=ics.GetVar("c")%>' 
        cid='<%=ics.GetVar("cid")%>'
        tname='<%=ics.GetVar("HeadVar")%>'>
</render:calltemplate>

See Also

RENDER.LOOKUP

		Home >	Contents >	Index >
	Oracle XML Tag Reference Copyright (c) 2013, 2016, Oracle and/or its affiliates. All rights reserved.