Tag File Elements
A TLD can also include declarations of tag files, described in Chapter 11, with any number of
<tag-file>
elements following the <tag> elements, if
any. The <tag-file> element contains other
elements that describe different aspects of the custom action. In
order, they are <description>,
<display-name>,
<icon>, <name>,
<path>, and
<example>.
The <description>,
<display-name>, and
<icon> elements are all optional and can be
used to describe each tag file in the same way as for other tag
library artifacts.
The
<name> element
is mandatory and contains the name for the corresponding custom
action element in the JSP pages. It must be a name that is unique
among tags and tag files in the tag library.
The mandatory <path> element contains the
path to the tag file. If the tag file is packaged together with the
TLD in a JAR file, it must start with
/META-INF/tags, and consequently, the tag file
must be located somewhere in this structure in the JAR file. If the
tag file and the TLD reside directly in the web application structure
(e.g., during development), the path must start with
/WEB-INF/tags.
An optional <example> element can be used to
include an example of how the custom action implemented by the tag
file should be used, just as for the <tag>
element.
Get JavaServer Pages, 3rd Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
