Home > Contents > Index >
Template Tags TOC | Alpha TOC | Tag Family TOC | Purpose TOC | Annotated TOC | Index
Render Tags
Content Server renders content in three ways:
- By rendering pages and pagelets into static HTML files through the Export to Disk publishing method.
- By rendering pages and pagelets dynamically when a visitor requests them on a dynamic public site.
- By rendering assets in response to the Preview function on a management or development system.
CS determines how to render content by using an argument named
rendermode
, which has three primary settings:
export
- uses the Export to Disk publishing method to create static HTML fileslive
- invokes Content Server to serve content dynamicallypreview
- invokes Content Server to render a selected asset in a browser pointed at a management or development system
rendermode
is set through theresargs
of page entries in the SiteCatalog table. When CS-Direct creates page entries for templates, it setsrendermode
as an argument in theresargs
columns for that entry and sets it tolive
. If you export or preview an asset that uses that template, CS-Direct sets rendermode toexport
orpreview
, as appropriate.The
render
tags process your page and element requests and create URLs and arguments for URLs. Some of the tags (render:callelement
andrender:satellitepage ,
for example) function similarly to tags that are available through Content Server or CS-Satellite. However, therender
tags preserve the CS-Direct rendering environment and the variables needed in that environment without requiring additional code.
Note
Each JSP file that includes
render
tags must have the following directive at the top:
<%@ taglib prefix="render" uri="futuretense_cs/render.tld" %>
Home > Contents > Index > FatWire JSP Tag Reference
Copyright 2005,2006,2007 by FatWire Software
All rights reserved.