pass arguments for that computation. These mechanisms can be subsumed directly into an
empty bodied action invocation, perhaps using attributes to describe the template and/or the
arguments for the computation.
An HTML quoting action
The final example is an action that takes its body and performs HTML quoting. In this case,
method will save away the value of the out implicit object and request
the evaluation of the body. The
method will take the nested stream,
perform the quoting, and send it down to the saved out stream.
A useBean as in the JSP 0.92 specification
The 0.92 public draft of the JSP specification included a version of a
a variation: if the Bean created included a
method then the method would be invoked. Observant readers will notice that a
is a special case of a
as the request object is one of
the objects available in
is a collection of actions that encapsulate some functionality to be used from within
a JSP page. A Tag library is made available to a JSP page via a
directive that identifies
the Tag Library via a URI (Universal Resource Identifier).
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.
The URI identifying the tag library is associated with a
Tag Library Description
classes as indicated in Section 5.3 below.
Packaged Tag Libraries
JSP page authoring tools are required to accept a Tag Library that is packaged as a JAR file.
When packaged sot he JAR file must have a tag library descriptor file named META INF/
JavaServer Pages 1.1 Specification
November 30, 1999