1
<?xml version="1.0" encoding="UTF-8"?>
2
<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
3
targetNamespace="http://java.sun.com/xml/ns/j2ee"
4
xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
5
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
6
elementFormDefault="qualified"
7
attributeFormDefault="unqualified"
11
@(#)jsp_2_0.xsds 1.17 03/18/03
18
Copyright 2002 Sun Microsystems, Inc., 901 San Antonio
19
Road, Palo Alto, California 94303, U.S.A. All rights
22
Sun Microsystems, Inc. has intellectual property rights
23
relating to technology described in this document. In
24
particular, and without limitation, these intellectual
25
property rights may include one or more of the U.S. patents
26
listed at http://www.sun.com/patents and one or more
27
additional patents or pending patent applications in the
28
U.S. and other countries.
30
This document and the technology which it describes are
31
distributed under licenses restricting their use, copying,
32
distribution, and decompilation. No part of this document
33
may be reproduced in any form by any means without prior
34
written authorization of Sun and its licensors, if any.
36
Third-party software, including font technology, is
37
copyrighted and licensed from Sun suppliers.
39
Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
40
JavaServer Pages, Enterprise JavaBeans and the Java Coffee
41
Cup logo are trademarks or registered trademarks of Sun
42
Microsystems, Inc. in the U.S. and other countries.
44
Federal Acquisitions: Commercial Software - Government Users
45
Subject to Standard License Terms and Conditions.
53
This is the XML Schema for the JSP 2.0 deployment descriptor
54
types. The JSP 2.0 schema contains all the special
55
structures and datatypes that are necessary to use JSP files
56
from a web application.
58
The contents of this schema is used by the web-app_2_4.xsd
59
file to define JSP specific content.
67
The following conventions apply to all J2EE
68
deployment descriptor elements unless indicated otherwise.
70
- In elements that specify a pathname to a file within the
71
same JAR file, relative filenames (i.e., those not
72
starting with "/") are considered relative to the root of
73
the JAR file's namespace. Absolute filenames (i.e., those
74
starting with "/") also specify names in the root of the
75
JAR file's namespace. In general, relative names are
76
preferred. The exception is .war files where absolute
77
names are preferred for consistency with the Servlet API.
82
<xsd:include schemaLocation="j2ee_1_4.xsd"/>
85
<!-- **************************************************** -->
87
<xsd:complexType name="jsp-configType">
91
The jsp-configType is used to provide global configuration
92
information for the JSP files in a web application. It has
93
two subelements, taglib and jsp-property-group.
99
<xsd:element name="taglib"
100
type="j2ee:taglibType"
102
maxOccurs="unbounded"/>
103
<xsd:element name="jsp-property-group"
104
type="j2ee:jsp-property-groupType"
106
maxOccurs="unbounded"/>
108
<xsd:attribute name="id" type="xsd:ID"/>
111
<!-- **************************************************** -->
113
<xsd:complexType name="jsp-fileType">
117
The jsp-file element contains the full path to a JSP file
118
within the web application beginning with a `/'.
124
<xsd:restriction base="j2ee:pathType"/>
128
<!-- **************************************************** -->
130
<xsd:complexType name="jsp-property-groupType">
134
The jsp-property-groupType is used to group a number of
135
files so they can be given global property information.
136
All files so described are deemed to be JSP files. The
137
following additional properties can be described:
139
- Control whether EL is ignored
140
- Control whether scripting elements are invalid
141
- Indicate pageEncoding information.
142
- Indicate that a resource is a JSP document (XML)
143
- Prelude and Coda automatic includes.
149
<xsd:group ref="j2ee:descriptionGroup"/>
150
<xsd:element name="url-pattern"
151
type="j2ee:url-patternType"
152
maxOccurs="unbounded"/>
153
<xsd:element name="el-ignored"
154
type="j2ee:true-falseType"
159
Can be used to easily set the isELIgnored
160
property of a group of JSP pages. By default, the
161
EL evaluation is enabled for Web Applications using
162
a Servlet 2.4 or greater web.xml, and disabled
168
<xsd:element name="page-encoding"
174
The valid values of page-encoding are those of the
175
pageEncoding page directive. It is a
176
translation-time error to name different encodings
177
in the pageEncoding attribute of the page directive
178
of a JSP page and in a JSP configuration element
179
matching the page. It is also a translation-time
180
error to name different encodings in the prolog
181
or text declaration of a document in XML syntax and
182
in a JSP configuration element matching the document.
183
It is legal to name the same encoding through
189
<xsd:element name="scripting-invalid"
190
type="j2ee:true-falseType"
195
Can be used to easily disable scripting in a
196
group of JSP pages. By default, scripting is
202
<xsd:element name="is-xml"
203
type="j2ee:true-falseType"
208
If true, denotes that the group of resources
209
that match the URL pattern are JSP documents,
210
and thus must be interpreted as XML documents.
211
If false, the resources are assumed to not
212
be JSP documents, unless there is another
213
property group that indicates otherwise.
218
<xsd:element name="include-prelude"
221
maxOccurs="unbounded">
225
The include-prelude element is a context-relative
226
path that must correspond to an element in the
227
Web Application. When the element is present,
228
the given path will be automatically included (as
229
in an include directive) at the beginning of each
230
JSP page in this jsp-property-group.
235
<xsd:element name="include-coda"
238
maxOccurs="unbounded">
242
The include-coda element is a context-relative
243
path that must correspond to an element in the
244
Web Application. When the element is present,
245
the given path will be automatically included (as
246
in an include directive) at the end of each
247
JSP page in this jsp-property-group.
253
<xsd:attribute name="id" type="xsd:ID"/>
256
<!-- **************************************************** -->
258
<xsd:complexType name="taglibType">
262
The taglibType defines the syntax for declaring in
263
the deployment descriptor that a tag library is
264
available to the application. This can be done
265
to override implicit map entries from TLD files and
272
<xsd:element name="taglib-uri"
277
A taglib-uri element describes a URI identifying a
278
tag library used in the web application. The body
279
of the taglib-uri element may be either an
280
absolute URI specification, or a relative URI.
281
There should be no entries in web.xml with the
282
same taglib-uri value.
288
<xsd:element name="taglib-location"
289
type="j2ee:pathType">
293
the taglib-location element contains the location
294
(as a resource relative to the root of the web
295
application) where to find the Tag Library
296
Description file for the tag library.
303
<xsd:attribute name="id" type="xsd:ID"/>