A JSP container can include a mechanism for being notified if an included file changes, so
the container can recompile the JSP page. However, the JSP 1.1 specification does not have
a way of directing the JSP container that included files have changed.
The following example requests the inclusion, at translation time, of a copyright file. The file
may have elements which will be processed too.
<%@ include file= copyright.html %>
<%@ include file="relativeURLspec" %>
The set of significant tags a JSP container interprets can be extended through a tag library .
directive in a JSP page declares that the page uses a tag library, uniquely
identifies the tag library using a URI and associates a tag prefix that will distinguish usage of
the actions in the library.
The URI identifying a tag library may be any valid URI as long as it can be used to uniquely
identify the semantics of the tag library. A common mechanism is to encoding the version of
a tag library into its URI.
If a JSP container implementation cannot locate (following the rules described in
Section 5.3.1) a tag library description for a given URI, a fatal translation error shall result.
It is a fatal translation error for the
directive to appear after actions using the prefix
introduced by the
See Chapter 5 for more specification details, and Section B.2 for an implementation note.
In the following example, a tag library is introduced and made available to this page using
prefix; no other tags libraries should be introduced in this page using this prefix.
In this particular case, we assume the tag library includes a
element type, which is
used within the page.
JavaServer Pages 1.1 Specification
November 30, 1999