Home >	Contents >	Index >

Template Tags TOC   |    Alpha TOC   |    Tag Family TOC   |    Purpose TOC   |    Annotated TOC   |    Index

ics:callelement

Processes the content of an element.

Syntax

<ics:callelement element="element name"> 
      <ics:argument name="argument name" value="arg value"/>
</ics:callelement>

Parameters

element (required)

Name of the element to call.

Description

The ics:callelement tag processes the content of an element. The element must exist in the ElementCatalog.

Variables that exist prior to ics:callelement are available to tags within the called element. Variables set within the called element are available in the parent element after the ics:callelement tag. Variables can also be set using the ics:argument tag within the ics:callelement tag.

Variables for the ics:callelement tag are subject to an order of precedence. The order of precedence is relative to the location of the variable. The following list describes the order of precedence:

1. Variables set in arguments

2. Variables set in scripts

3. resdetails1 and resdetails2 of the ElementCatalog

In the following element, the arg=3 variable is set in the resdetails1 column in the ElelementCatalog. The arg value with the highest order of precedence is value1.

<ics:setvar name="arg" value="value2"/>
...
<ics:callelement element="element name">
  <ics:argument name="arg" value="value1"/>
</ics:callelement>

In the following element, the arg=value3 is set in the redetails1 column in the ElementCatalog. The arg value with the highest order of precedence is value2.

<ics:setvar name="arg" value="value2"/>
...
<ics:callelement element="element name">
</ics:callelement>

In the following element, the arg=value3 is set in the resdetails1 column of the ElementCatalog. The arg value with the highest order of precedence is value3; this is occurs when a variable is not defined in scope before the ics:callelement tag.

 <ics:callelement name="element name">
 </ics:callelement>

The tag also supports 'custom elements' feature. If there exist a custom element for passed-in 'element' value then Sites will call that custom element instead of original element.
For example, if element 'CustomElements/fatwire/ui/util/ValidateFileUpload' has been implemented as custom implementation then existing element 'fatwire/ui/util/ValidateFileUpload' will not be called when below tag executes -

<ics:callelement element="fatwire/ui/util/ValidateFileUpload">

For scenario where inspite of having custom element, requirement is to ignore custom element and call original element, use brackets in element name -
<ics:callelement element="[fatwire/ui/util/ValidateFileUpload]">
Above tag will execute the exact element (fatwire/ui/util/ValidateFileUpload), not the one present inside CustomElements folder.
Note: The tag ics.isElement(elementName) does not support bracket in element name.

Error Numbers

The possible values of errno include:

Value	Description
-10	No element exists.
-12	Cannot evaluate element.

Example

The following example calls the element SimpleTest with the arguments Foo and Foo2.

<ics:clearerrno/>
<ics:callelement element="SimpleTest">
     <ics:argument name="Foo" value="Bar"/>
     <ics:argument name="Foo2" value="Bar2"/>
</ics:callelement>
<ics:if condition='<%=ics.GetErrno()!=0%>'>
      <ics:then>
       Problem running element SimpleTest
      </ics:then>
</ics:if>

See Also

ics:argument

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