Examples

In the next example, the current date is inserted.

<%= (new java.util.Date()).toLocaleString() %>

Syntax

<%= 

expression

 %>

2.11

Actions

Actions

 may affect the current 

out

 stream and use, modify and/or create objects. Actions may, 

and often will, depend on the details of the specific request object received by the JSP page.

The JSP specification includes some action types that are 

standard

 and must be implemented 

by all conforming JSP containers. New action types are introduced using the 

taglib

directive. 

The syntax for action elements is based on XML; the only transformation needed is due to 

quoting conventions (see Section 7.5).

2.12

Tag Attribute Interpretation Semantics

Generally, all custom and standard action attributes and their values either remain 

uninterpreted by, or have well defined action type specific semantics known to, a conforming 

JSP container. However there are two exceptions to this general rule: some attribute values 

represent request time attribute values and are processed by a conforming JSP container, and 

the id and scope attributes have special interpretation.

2.12.1

Request Time Attribute Values

Action elements (both standard and custom) can define named attributes and associated 

values. Typically a JSP page treats these values as fixed and immutable but the JSP 1.1 

provides a mechanism to describe a value that is computed at request time.

57

JavaServer Pages 1.1 Specification  

November 30, 1999