About the static JavaServer Page tag
JSP tag to cause one or more static file bundles,
individual text files, or individual binary files to be included in the current stream. A static
sent to a browser session together in one HTTP response, to reduce HTTP traffic and improve
response time to the browser user.
<pega:static type="script" app="webwb" > <pega:bundle name="pega_tools" /> <pega:bundle name="acmestyles" /> <pega:file name="markov.js" /> <pega:binaryfile name="johnson.gif" app="webwb" /> </pega:static>
When to use
For example, when entering HTML source code directly into the HTML tab of a control rule (or similar form), you can minimize the size of the resulting HTML document with the <pega:onlyonce >, <pega:bundle> and <pega:static > tags.
In the syntax presentation below:
- JSP delimiters <pega:...> and </pega:...> mark the start and end of the tag.
- Replace any text in italics with your choice of value of that type.
<pega:static app="applicationname" type="type"> <!-- one or more pega:bundle JSP tags --> <!-- one or more pega:file JSP tags --> </pega:static>
type attribute is required.
You can include a pega:when tag within the static tag scope, to conditionalize which bundles or files are included.
References to CSS files (in the form of the <link rel="stylesheet" ...> tag) must appear within the <head> element of an HTML document. In contrast, a <script ..> tag can appear anywhere in the document.
|The first key part ( Application Name Directory ) of the text file rule included in the <pega:static..> tag. All files included within one <pega:static ..> tag must have a common Application Name|
| One of two values to identify the type of content in the bundle rules: |
|Reserved. Do not use.|
Previous topic JavaServer Pages tags Next topic acDataSource JavaServer Page tag