...
| Table of Contents | ||
|---|---|---|
|
...
Contents of a JSP
A JSP file contains simply the (X)HTML (or XML) that is requested. JSP directives allow the use of so-called tag libraries. To use the core functions of the JSP Standard Tag Library (JSTL), the following directive should be placed at the beginning of the file:
...
The following fields can be used in the XML descriptor files associated with each JSP. The options are:
| Tag | Note | Description |
|---|---|---|
| Required | The unique internal name for the design template. |
| Required | The name shown in the drop-down list for the element. |
| Several are possible | Specifies for which part in XperienCentral the descriptor is intended. |
| Optional | Disk location of the handling JSPF for the server side include version. |
| Optional and several are possible | Definitions of the options to be configured in XperienCentral. |
| Optional and several are possible | Definitions of the channels. |
Property Tags, Design Template Variants and Styles
...
The possible property tags are:
| Tag | Note | Description |
|---|---|---|
| Required | The name as it is used as identifier in the JSP. |
| Required | The name as appears in XperienCentral drop-down lists. |
| Required | The options are "Boolean", "String", and "Integer". |
| Optional | If no style property is connected to a design template property, the default value is used. |
The integer, string, and boolean data types make it possible to configure the JSPs without having to use Java code. If possible, create a pagemetadata plugin if you want to assign specific objects to a page.
...
A channel can be viewed using the ?channel=… query argument on a page, for example http://localhost:8080/web/show/?channel=pdf.
Example uses are:
| Channel-name | Usage |
|---|---|
| Generates plain text. |
| Generates plain text used by the Newsletter component. |
| Generates HTML used by the Newsletter component. |
| Generates the design template in PDF. |
mobile | Generates HTML for mobile devices. |
If a design template does not specify a channel, this item will be skipped when rendering. For example, if a table element should not be rendered for a newsletter, do not add channel textmail or htmlmail to the table element design template(s).
The styles included in XperienCentral has tags with the following meaning:
| Tag | Note | Description |
|---|---|---|
| Required | The frame identifier. |
| Required | The relative path to the JSP. |
If the website uses HTML frames, the content of the frames is specified using a frame tag in the JSP’s design template descriptor that contains the frame set. The XML looks as follows (using sample entries):
...
The tags have the following meaning:
| Tag | Note | Description |
|---|---|---|
| Required | The frame identifier. |
| Required | Relative path to the JSP. |
To use such a frame in the JSP, create a link in the URL with frame=<frame identifier>. For the XML example above, the link is as follows:
...
The tags have the following meanings:
| Tag | Note | Description |
|---|---|---|
| Required | The stylesheet identifier. |
| Required | The relative path to the stylesheet. |
pagedependent | Required | A boolean that determines whether the content of the stylesheet is determined by limitations set in the XperienCentral style and that are valid for that page. |
This does not mean that the stylesheet is automatically included in the source. This is accomplished by requesting the current page from the design templatecontext, and then requesting all the connected stylesheets from that page. This generates an array of stylesheet objects that each generate the URL using the getUrl() method.
...