Invokes a Template, as either a pagelet or an element, for the purpose of rendering an asset.
<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"] [ELEMENTPATH="absolute"] > </RENDER.CALLTEMPLATE>
ttypeshould be set to
CSElement. The default value is
CSElementis the other legal value. See
tnameare set, then
contextdata is ignored.
cidare set. If these three attributes are not set, the called template will be determined by looking at
tnamerefers to a typeless template, prefix the template name with '/' (/templatename).
tnameare 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
contextvalue 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
contextdata to be set automatically. Manually overriding this value should be considered an advanced technique.
pagelet. Setting this attribute value to
elementwill 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).
This tag is the preferred method for invoking a template. It effectively replaces
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
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
RENDER.CALLTEMPLATE operates in two modes: explicit mode and context mode.
In explicit mode,
tname are explicitly specified as attributes to the tag. In essence, the asset identified by
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.
The possible values of
A required parameter is missing .
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>
|Home >||Contents >||Index >|
Oracle XML Tag Reference