Custom tags are user-defined JSP language elements that encapsulate recurring tasks. Custom tags are distributed in a tag library, which defines a set of related custom tags and contains the objects that implement the tags.
Custom tags have the syntax
<prefix:tag attr1="value" ... attrN="value" />
<prefix:tag attr1="value" ... attrN="value" > body </prefix:tag>
where prefix distinguishes tags for a library, tag is the tag identifier, and attr1 ... attrN are attributes that modify the behavior of the tag.
To use a custom tag in a JSP page, you must
See Chapter 7 for detailed information on the different types of tags and how to implement tags.
Declaring Tag Libraries
To declare that a JSP page will use tags defined in a tag library, you include a taglib directive in the page before any custom tag from that tag library is used. If you forget to include the taglib directive for a tag library in a JSP page, the JSP compiler will treat any invocation of a custom tag from that library as static data and will simply insert the text of the custom tag call into the response.
<%@ taglib prefix="tt" [tagdir=/WEB-INF/tags/dir | uri=URI] %>
The prefix attribute defines the prefix that distinguishes tags defined by a given tag library from those provided by other tag libraries.
If the tag library is defined with tag files (see Encapsulating Reusable Content Using Tag Files, page 212), you supply the tagdir attribute to identify the location of the files. The value of the attribute must start with /WEB-INF/tags/. A translation error will occur if the value points to a directory that doesn't exist or if it is used in conjunction with the uri attribute.
The uri attribute refers to a URI that uniquely identifies the tag library descriptor (TLD), a document that describes the tag library (see Tag Library Descriptors, page 229).
Tag library descriptor file names must have the extension .tld. TLD files are stored in the WEB-INF directory or subdirectory of the WAR file, or in the META-INF/ directory or subdirectory of a tag library packaged in a JAR. You can reference a TLD directly or indirectly.
The following taglib directive directly references a TLD file name:
<%@ taglib prefix="tlt" uri="/WEB-INF/iterator.tld"%>
This taglib directive uses a short logical name to indirectly reference the TLD:
<%@ taglib prefix="tlt" uri="/tlt"%>
The iterator example defines and uses a simple iteration tag. The JSP pages use a logical name to reference the TLD.
To deploy and run the iterator application with NetBeans 5.5, follow these steps:
To deploy and run the iterator application with Ant, follow these steps:
To learn how to configure the example, refer to the deployment descriptor, which includes the following configurations:
The absolute URIs for the JSTL library are as follows:
When you reference a tag library with an absolute URI that exactly matches the URI declared in the taglib element of the TLD (see Tag Library Descriptors, page 229), you do not have to add the taglib element to web.xml; the JSP container automatically locates the TLD inside the JSTL library implementation.
Including the Tag Library Implementation
In addition to declaring the tag library, you also must make the tag library implementation available to the web application. There are several ways to do this. Tag library implementations can be included in a WAR in an unpacked format: Tag files are packaged in the /WEB-INF/tag/ directory, and tag handler classes are packaged in the /WEB-INF/classes/ directory of the WAR. Tag libraries already packaged into a JAR file are included in the /WEB-INF/lib/ directory of the WAR. Finally, an application server can load a tag library into all the web applications running on the server. For example, in the Application Server, the JSTL TLDs and libraries are distributed in the archive appserv-jstl.jar in <JAVAEE_HOME>/lib/. This library is automatically loaded into the classpath of all web applications running on the Application Server, so you don't need to add it to your web application.
The iterator tag library is implemented with tag handlers. Therefore, its implementation classes are packaged in the /WEB-INF/classes/ directory.