Home >	Contents >	Index >

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

Render Tags

Sites 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.

Sites 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 files
• live - invokes Sites to serve content dynamically
• preview - invokes Sites to render a selected asset in a browser pointed at a management or development system

rendermode is set through the resargs of page entries in the SiteCatalog table. When Sites creates page entries for templates, it sets rendermode as an argument in the resargs columns for that entry and sets it to live. If you export or preview an asset that uses that template, Sites sets rendermode to export or preview, as appropriate.

The render tags process your page and element requests and create URLs and arguments for URLs. Some of the tags (render:callelement and render:satellitepage , for example) function similarly to tags that are available through Sites or Sites-Satellite. However, the render tags preserve the Sites 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 >
	Oracle JSP Tag Reference Copyright (c) 2013, 2015, Oracle and/or its affiliates. All rights reserved.