• <view:define name="foo" value="bar"/>
• <view:define name="foo">bar</view:define>

Allows a short-hand way to declare many simple variables as attributes of the def tag. Only supports values that are literals. Use the view:define tag for non-literal values.

Example: <view:def color="blue" shape="round"/> will create two script variables, color with a value of blue and shape with a value of round.

Prints out a script variable. There are a few forms the out tag can take:

• <view:out name="variableName">defaultValue</view:out>, where variableName is the script variable name, and defaultValue is the value that will be printed out if variableName is empty.
• &view:out-variableName; or &view:out-name:variableName;, where variableName is the script variable name. A defaultValue is not supported with this syntax. This syntax is the alternate tag syntax defined in TagMatchers.xml.

(To support these multiple syntaxes, a name attribute is not formally declared on this tag. Instead the dynamic attributes are used to figure out the name of the script variable.)

Used inside a page that is included by another page. It allows the included page to specify a script variable that is required by the included page. If the page that includes the included file does not define that variable, an exception will be generated, unless a default value is specified as part of this tag. A default value is specified in the body of the tag. Examples:

<view:includeparam name="foo"/> (Will throw exception if foo is not defined)

<view:includeparam name="foo">defaultValue</view:includeparam> (If foo is not defined by the including page, then foo's value will be defaultValue.)

Prints out a resource value, based on the currently defined locale. The resource must be located in a bundle that was defined with the view:resourcebundle tag. The bundle attribute of this tag can be used to specify a specifc bundle to use to find the resource. If no bundle name is specified, then all resource bundles that were defined as part of the page will be searched. There are a few forms the out tag can take:

• <view:res name="resName">defaultValue</view:out> or <view:res name="resName" bundle="bundleName">defaultValue</view:out>, where resName is the script variable name, and defaultValue is the value that will be printed out if resName is empty.
• &view:out-resName; or &view:out-name:resName; or &view:out-name:resName-bundle:bundleName;, where resName is the script variable name. A defaultValue is not supported with this syntax. This syntax is the alternate tag syntax defined in TagMatchers.xml.

(To support these multiple syntaxes, a name attribute is not formally declared on this tag. Instead the dynamic attributes are used to figure out the name of the resource key.)

A wrapper tag that is required if the view:elsif and/or view:else tags are to be used with a view:if tag. Example:

<view:choose> <view:if><view:test>value == 'one'</view:test> Value is one. </view:if> <view:elseif><view:test>value == 'two'</view:test> Value is two. </view:elseif> <view:else> Value is not one or two. </view:else> </view:choose>

Only includes the body of the tag if a view:test expression evaluates to true in the scripting language. There are two ways to use this tag:

• Single if statement, no associated elseif/else cases:
  <view:if><test>value == 'one'</test></view:if>
  
• Part of a if/elseif/else set (see view:choose example).

Used as part of an if/elseif/else set. It should have a nested view:test tag. See view:choose example.

Used as part of an if/elseif/else set. The body of the tag is included in the page output when the associated if/elseif tests fail. See view:choose example.

Used as a child of view:if or view:elseif. The body of the view:test tag is a script expression that should be interpreted as a true/false result. The boolean result is communicated to the parent view:if or view:elseif tag. See view:choose example for usage.

The body of the tag does *not* have to be XML escaped (for instance, < does not have to be written as &lt;). This means the source document that has this tag will not validate as valid XML. If you want have the source validate, then declare an overlay in your tagnetic config file that will XML unescape the body of the tag before it is sent to the script engine. Make sure to set the priority to 0 so that the overlay executes before the normal view:test tag handler.

If you use the overlay, then you can write the script in XML escaped format. For instance, the script expression "value < 5" would be written as: <view:test>value &lt; 5</view:test>.

The body of the tag does *not* have to be XML escaped (for instance, < does not have to be written as &lt;). This means the source document that has this tag will not validate as valid XML. If you want have the source validate, then declare an overlay in your tagnetic config file that will XML unescape the body of the tag before it is sent to the script engine. Make sure to set the priority to 0 so that the overlay executes before the normal view:script tag handler.

<tags nsprefix="view" scriptcontextname="js" scriptcontext="org.tagnetic.core.scriptcontext.implementer.javascript.JavaScriptContext"> <tag name="script" classname="org.tagnetic.core.tags.XmlUnEscapeTag" priority="0"/> </tags>

If you use the overlay, then you can write the script in XML escaped format. For instance, the script expression "value = ''" would be written as: <view:script>value = '&lt;weirdstring&gt;'</view:script>.

Allows iteration over simple integer increment count, a script array, or the properties in a script object. Each successful iteration will output the body of the tag.

• Integer iteration: To use a simple iteration, do not specify a value for the object attribute. The start and end attributes are required. The example below iterates to 10 in steps of 2. The body of the view:foreach tag will be outputted 5 times. loopStatus is the default loopstatusvar. See that attribute for details:

  <view:foreach start="0" end="10" step="2"> Index value is: <view:out name="loopStatus.currentIndex"/><br> </view:foreach>

• Array iteration: To iterate over a script array, give the script array variable name as the value to the object attribute. The start, end, and step attributes can be used to control what array indices are used in the iterations. Example:

  <view:script> function Pair(name, value) { this.name = name; this.value = value; } var testArray = new Array(); testArray[0] = new Pair('heavy', 'blue'); testArray[1] = new Pair('light', 'green'); testArray[2] = new Pair('heavy', 'red'); </view:script> <view:foreach object="testArray" var="pair"> <p>Current index is [&view:out-loopStatus.currentIndex;]<br> Current loop count is [&view:out-loopStatus.loopCount;]<br> My pair's weight is [&view:out-pair.name;], color is [&view:out-pair.value;]</p> </view:foreach>

• Object member iteration: iterates over the members of an object. Similar to the for (param in object) iteration available in javascript. To use this type of iteration, give the script variable name for the object as the value of the object attribute. The The start, end, and step attributes don't have meaning in this type of iteration. Example:

  <view:script> var testObject = { name: 'Washing machine', stockNumber: 3343200, price: '$2.00', quantity: 5 }; </view:script> <view:foreach object="testObject" var="propValue"> Member name: [&view:out-loopStatus.propertyKey;], value is [&view:out-propValue;]<br /> </view:foreach>

Loads XML into a script variable. If javascript is the script language, then the E4X language extensions are used to manipulate the data in script.

Inserts the collection of tags that match the name attribute. It essentially dumps the tags that are collected by the TagCollector class. The TagCollector class is used in HtmlTags.xml to collect script, link and style tags.

You do not need to use the tagcollection tag if you want the collected tags to be inserted as children of the HTML HEAD element. The TagCollector class automatically puts in a post file filter that uses the TagCollection class to insert all collected tags in the HEAD element.

However, if you want more control over where the tags are outputted, use this tag. Once the collection of tags with the specified tag name is outputted with this tag, they will not be dumped as part of the post file filter process in the HEAD area.

HTML-escapes some characters in the body of the tag:

• < converts to &lt;
• > converts to &gt;
• & converts to &amp;