The default character set encoding is ISO 8859 1 (also known as latin 1).

A JSP container may use some implementation dependent heuristics and/or structure to 

determine what is the expected character encoding of a JSP page and then verify that 

contentType

 attribute is as expected.

A JSP container will raise a translation time error if an unsupported character encoding is 

requested.

See Section B.1 for some implementation notes.

2.7.5

Including Data in JSP Pages

Including data is a significant part of the tasks in a JSP page. Accordingly, the JSP 1.1 

specification has two include mechanisms suited to different tasks. A summary of their 

semantics is shown in 

TABLE 2 1

.

TABLE 2 1 

Summary of Include Mechanisms in JSP 1.1

Syntax

What

Phase

Spec

Object

Description

Section

<%@ include file=... %>

directive

translation 

virtual

static

Content is parsed by 

2.7.6

time

JSP container.

action

request time

virtual

static

Content is not parsed; it 

2.13.4

and 

is included in place.

dynamic

The 

Spec

 column describes what type of specification is valid to appear in the given element. 

The JSP specification requires a relative URL spec as described in Section 2.5.2. The 

reference is resolved by the Web/Application server and its URL map is involved.

An include directive regards a resource like a JSP page as a static object; i.e. the bytes in the 

JSP page are included. An include action regards a resource like a JSP page as a dynamic 

object; i.e. the request is sent to that object and the result of processing it is included.

2.7.6

The 

include

 Directive

The 

include

 directive is used to substitute text and/or code at JSP page translation time. 

The 

<%@ include file= relativeURLspec  %>

 directive inserts the text of the 

specified resource into the .

jsp

 file. The included file is subject to the access control 

available to the JSP container. The 

file

 attribute is as in Section 2.5.2.

Chapter 2

Standard Syntax and Semantics

50