JSP Directives

JSP directives provide directions and instructions to the container, telling it how to handle certain aspects of JSP processing.
Directives in JSPs are instruction from JSPs to JSP Engine. Directives are classified in 3 categories:

1. Page Directives.
2. Taglib Directives.
3. Include Directives.

Directive                 Description
<%@ page ... %>     Defines page-dependent attributes, such as scripting language, error page, and    buffering requirements.
<%@ include ... %>    Includes a file during the translation phase.
<%@ taglib ... %>      Declares a tag library, containing custom actions, used in the page

The page Directive:

The page directive is used to provide instructions to the container that pertain to the current JSP page. You may code page directives anywhere in your JSP page. By convention, page directives are coded at the top of the JSP page.

 Following is the basic syntax of page directive:

You can write XML equivalent of the above syntax as follows:

The include Directive:

The include directive is used to includes a file during the translation phase. This directive tells the container to merge the content of other external files with the current JSP during the translation phase. You may code include directives anywhere in your JSP page.

The general usage form of this directive is as follows:

The filename in the include directive is actually a relative URL. If you just specify a filename with no associated path, the JSP compiler assumes that the file is in the same directory as your JSP.

You can write XML equivalent of the above syntax as follows:

The taglib Directive:

​​​​​​​The JavaServer Pages API allows you to define custom JSP tags that look like HTML or XML tags and a tag library is a set of user-defined tags that implement custom behavior.

The taglib directive declares that your JSP page uses a set of custom tags, identifies the location of the library, and provides a means for identifying the custom tags in your JSP page.

The taglib directive follows the following syntax:

Where the uri attribute value resolves to a location the container understands and the prefix attribute informs a container what bits of markup are custom actions.

You can write XML equivalent of the above syntax as follows: