View | Details | Raw Unified | Return to bug 55166
Collapse All | Expand All

(-)java/javax/servlet/resources/jsp_2_0.xsd (+323 lines)
Line 0 Link Here
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"
8
	    version="2.0">
9
  <xsd:annotation>
10
    <xsd:documentation>
11
      @(#)jsp_2_0.xsds	1.17 03/18/03
12
    </xsd:documentation>
13
  </xsd:annotation>
14
15
  <xsd:annotation>
16
    <xsd:documentation>
17
18
      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
19
20
      Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
21
22
      The contents of this file are subject to the terms of either the
23
      GNU General Public License Version 2 only ("GPL") or the Common
24
      Development and Distribution License("CDDL") (collectively, the
25
      "License").  You may not use this file except in compliance with
26
      the License. You can obtain a copy of the License at
27
      https://glassfish.dev.java.net/public/CDDL+GPL.html or
28
      glassfish/bootstrap/legal/LICENSE.txt.  See the License for the
29
      specific language governing permissions and limitations under the
30
      License.
31
32
      When distributing the software, include this License Header
33
      Notice in each file and include the License file at
34
      glassfish/bootstrap/legal/LICENSE.txt.  Sun designates this
35
      particular file as subject to the "Classpath" exception as
36
      provided by Sun in the GPL Version 2 section of the License file
37
      that accompanied this code.  If applicable, add the following
38
      below the License Header, with the fields enclosed by brackets []
39
      replaced by your own identifying information:
40
      "Portions Copyrighted [year] [name of copyright owner]"
41
42
      Contributor(s):
43
44
      If you wish your version of this file to be governed by only the
45
      CDDL or only the GPL Version 2, indicate your decision by adding
46
      "[Contributor] elects to include this software in this
47
      distribution under the [CDDL or GPL Version 2] license."  If you
48
      don't indicate a single choice of license, a recipient has the
49
      option to distribute your version of this file under either the
50
      CDDL, the GPL Version 2 or to extend the choice of license to its
51
      licensees as provided above.  However, if you add GPL Version 2
52
      code and therefore, elected the GPL Version 2 license, then the
53
      option applies only if the new code is made subject to such
54
      option by the copyright holder.
55
56
    </xsd:documentation>
57
  </xsd:annotation>
58
59
  <xsd:annotation>
60
    <xsd:documentation>
61
      The Apache Software Foundation elects to include this software under the
62
      CDDL license.
63
    </xsd:documentation>
64
  </xsd:annotation>
65
66
  <xsd:annotation>
67
    <xsd:documentation>
68
69
      This is the XML Schema for the JSP 2.0 deployment descriptor
70
      types.  The JSP 2.0 schema contains all the special
71
      structures and datatypes that are necessary to use JSP files
72
      from a web application.
73
74
      The contents of this schema is used by the web-app_2_4.xsd
75
      file to define JSP specific content.
76
77
    </xsd:documentation>
78
  </xsd:annotation>
79
80
  <xsd:annotation>
81
    <xsd:documentation>
82
83
      The following conventions apply to all J2EE
84
      deployment descriptor elements unless indicated otherwise.
85
86
      - In elements that specify a pathname to a file within the
87
	same JAR file, relative filenames (i.e., those not
88
	starting with "/") are considered relative to the root of
89
	the JAR file's namespace.  Absolute filenames (i.e., those
90
	starting with "/") also specify names in the root of the
91
	JAR file's namespace.  In general, relative names are
92
	preferred.  The exception is .war files where absolute
93
	names are preferred for consistency with the Servlet API.
94
95
    </xsd:documentation>
96
  </xsd:annotation>
97
98
  <xsd:include schemaLocation="j2ee_1_4.xsd"/>
99
100
101
<!-- **************************************************** -->
102
103
  <xsd:complexType name="jsp-configType">
104
    <xsd:annotation>
105
      <xsd:documentation>
106
107
	The jsp-configType is used to provide global configuration
108
	information for the JSP files in a web application. It has
109
	two subelements, taglib and jsp-property-group.
110
111
      </xsd:documentation>
112
    </xsd:annotation>
113
114
    <xsd:sequence>
115
      <xsd:element name="taglib"
116
		   type="j2ee:taglibType"
117
		   minOccurs="0"
118
		   maxOccurs="unbounded"/>
119
      <xsd:element name="jsp-property-group"
120
		   type="j2ee:jsp-property-groupType"
121
		   minOccurs="0"
122
		   maxOccurs="unbounded"/>
123
    </xsd:sequence>
124
    <xsd:attribute name="id" type="xsd:ID"/>
125
  </xsd:complexType>
126
127
<!-- **************************************************** -->
128
129
  <xsd:complexType name="jsp-fileType">
130
    <xsd:annotation>
131
      <xsd:documentation>
132
133
	The jsp-file element contains the full path to a JSP file
134
	within the web application beginning with a `/'.
135
136
      </xsd:documentation>
137
    </xsd:annotation>
138
139
    <xsd:simpleContent>
140
      <xsd:restriction base="j2ee:pathType"/>
141
    </xsd:simpleContent>
142
  </xsd:complexType>
143
144
<!-- **************************************************** -->
145
146
  <xsd:complexType name="jsp-property-groupType">
147
    <xsd:annotation>
148
      <xsd:documentation>
149
150
	The jsp-property-groupType is used to group a number of
151
	files so they can be given global property information.
152
	All files so described are deemed to be JSP files.  The
153
	following additional properties can be described:
154
155
	    - Control whether EL is ignored
156
	    - Control whether scripting elements are invalid
157
	    - Indicate pageEncoding information.
158
	    - Indicate that a resource is a JSP document (XML)
159
	    - Prelude and Coda automatic includes.
160
161
      </xsd:documentation>
162
    </xsd:annotation>
163
164
    <xsd:sequence>
165
      <xsd:group ref="j2ee:descriptionGroup"/>
166
      <xsd:element name="url-pattern"
167
		   type="j2ee:url-patternType"
168
		   maxOccurs="unbounded"/>
169
      <xsd:element name="el-ignored"
170
		   type="j2ee:true-falseType"
171
		   minOccurs="0">
172
	<xsd:annotation>
173
	  <xsd:documentation>
174
175
	    Can be used to easily set the isELIgnored
176
	    property of a group of JSP pages.  By default, the
177
	    EL evaluation is enabled for Web Applications using
178
	    a Servlet 2.4 or greater web.xml, and disabled
179
	    otherwise.
180
181
	  </xsd:documentation>
182
	</xsd:annotation>
183
      </xsd:element>
184
      <xsd:element name="page-encoding"
185
		   type="j2ee:string"
186
		   minOccurs="0">
187
	<xsd:annotation>
188
	  <xsd:documentation>
189
190
	    The valid values of page-encoding are those of the
191
	    pageEncoding page directive.  It is a
192
	    translation-time error to name different encodings
193
	    in the pageEncoding attribute of the page directive
194
	    of a JSP page and in a JSP configuration element
195
	    matching the page.  It is also a translation-time
196
	    error to name different encodings in the prolog
197
	    or text declaration of a document in XML syntax and
198
	    in a JSP configuration element matching the document.
199
	    It is legal to name the same encoding through
200
	    mulitple mechanisms.
201
202
	  </xsd:documentation>
203
	</xsd:annotation>
204
      </xsd:element>
205
      <xsd:element name="scripting-invalid"
206
		   type="j2ee:true-falseType"
207
		   minOccurs="0">
208
	<xsd:annotation>
209
	  <xsd:documentation>
210
211
	    Can be used to easily disable scripting in a
212
	    group of JSP pages.  By default, scripting is
213
	    enabled.
214
215
	  </xsd:documentation>
216
	</xsd:annotation>
217
      </xsd:element>
218
      <xsd:element name="is-xml"
219
		   type="j2ee:true-falseType"
220
		   minOccurs="0">
221
	<xsd:annotation>
222
	  <xsd:documentation>
223
224
	    If true, denotes that the group of resources
225
	    that match the URL pattern are JSP documents,
226
	    and thus must be interpreted as XML documents.
227
	    If false, the resources are assumed to not
228
	    be JSP documents, unless there is another
229
	    property group that indicates otherwise.
230
231
	  </xsd:documentation>
232
	</xsd:annotation>
233
      </xsd:element>
234
      <xsd:element name="include-prelude"
235
		   type="j2ee:pathType"
236
		   minOccurs="0"
237
		   maxOccurs="unbounded">
238
	<xsd:annotation>
239
	  <xsd:documentation>
240
241
	    The include-prelude element is a context-relative
242
	    path that must correspond to an element in the
243
	    Web Application.  When the element is present,
244
	    the given path will be automatically included (as
245
	    in an include directive) at the beginning of each
246
	    JSP page in this jsp-property-group.
247
248
	  </xsd:documentation>
249
	</xsd:annotation>
250
      </xsd:element>
251
      <xsd:element name="include-coda"
252
		   type="j2ee:pathType"
253
		   minOccurs="0"
254
		   maxOccurs="unbounded">
255
	<xsd:annotation>
256
	  <xsd:documentation>
257
258
	    The include-coda element is a context-relative
259
	    path that must correspond to an element in the
260
	    Web Application.  When the element is present,
261
	    the given path will be automatically included (as
262
	    in an include directive) at the end of each
263
	    JSP page in this jsp-property-group.
264
265
	  </xsd:documentation>
266
	</xsd:annotation>
267
      </xsd:element>
268
    </xsd:sequence>
269
    <xsd:attribute name="id" type="xsd:ID"/>
270
  </xsd:complexType>
271
272
<!-- **************************************************** -->
273
274
  <xsd:complexType name="taglibType">
275
    <xsd:annotation>
276
      <xsd:documentation>
277
278
	The taglibType defines the syntax for declaring in
279
	the deployment descriptor that a tag library is
280
	available to the application.  This can be done
281
	to override implicit map entries from TLD files and
282
	from the container.
283
284
      </xsd:documentation>
285
    </xsd:annotation>
286
287
    <xsd:sequence>
288
      <xsd:element name="taglib-uri"
289
		   type="j2ee:string">
290
	<xsd:annotation>
291
	  <xsd:documentation>
292
293
	    A taglib-uri element describes a URI identifying a
294
	    tag library used in the web application.  The body
295
	    of the taglib-uri element may be either an
296
	    absolute URI specification, or a relative URI.
297
	    There should be no entries in web.xml with the
298
	    same taglib-uri value.
299
300
	  </xsd:documentation>
301
	</xsd:annotation>
302
      </xsd:element>
303
304
      <xsd:element name="taglib-location"
305
		   type="j2ee:pathType">
306
	<xsd:annotation>
307
	  <xsd:documentation>
308
309
	    the taglib-location element contains the location
310
	    (as a resource relative to the root of the web
311
	    application) where to find the Tag Library
312
	    Description file for the tag library.
313
314
	  </xsd:documentation>
315
	</xsd:annotation>
316
      </xsd:element>
317
318
    </xsd:sequence>
319
    <xsd:attribute name="id" type="xsd:ID"/>
320
  </xsd:complexType>
321
322
</xsd:schema>
323
(-)java/javax/servlet/resources/jsp_2_1.xsd (+356 lines)
Line 0 Link Here
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/javaee"
4
	    xmlns:javaee="http://java.sun.com/xml/ns/javaee"
5
	    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
6
	    elementFormDefault="qualified"
7
	    attributeFormDefault="unqualified"
8
	    version="2.1">
9
  <xsd:annotation>
10
    <xsd:documentation>
11
      @(#)jsp_2_1.xsds	1.5 08/11/05
12
    </xsd:documentation>
13
  </xsd:annotation>
14
15
  <xsd:annotation>
16
    <xsd:documentation>
17
18
      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
19
20
      Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
21
22
      The contents of this file are subject to the terms of either the
23
      GNU General Public License Version 2 only ("GPL") or the Common
24
      Development and Distribution License("CDDL") (collectively, the
25
      "License").  You may not use this file except in compliance with
26
      the License. You can obtain a copy of the License at
27
      https://glassfish.dev.java.net/public/CDDL+GPL.html or
28
      glassfish/bootstrap/legal/LICENSE.txt.  See the License for the
29
      specific language governing permissions and limitations under the
30
      License.
31
32
      When distributing the software, include this License Header
33
      Notice in each file and include the License file at
34
      glassfish/bootstrap/legal/LICENSE.txt.  Sun designates this
35
      particular file as subject to the "Classpath" exception as
36
      provided by Sun in the GPL Version 2 section of the License file
37
      that accompanied this code.  If applicable, add the following
38
      below the License Header, with the fields enclosed by brackets []
39
      replaced by your own identifying information:
40
      "Portions Copyrighted [year] [name of copyright owner]"
41
42
      Contributor(s):
43
44
      If you wish your version of this file to be governed by only the
45
      CDDL or only the GPL Version 2, indicate your decision by adding
46
      "[Contributor] elects to include this software in this
47
      distribution under the [CDDL or GPL Version 2] license."  If you
48
      don't indicate a single choice of license, a recipient has the
49
      option to distribute your version of this file under either the
50
      CDDL, the GPL Version 2 or to extend the choice of license to its
51
      licensees as provided above.  However, if you add GPL Version 2
52
      code and therefore, elected the GPL Version 2 license, then the
53
      option applies only if the new code is made subject to such
54
      option by the copyright holder.
55
56
    </xsd:documentation>
57
  </xsd:annotation>
58
59
  <xsd:annotation>
60
    <xsd:documentation>
61
      The Apache Software Foundation elects to include this software under the
62
      CDDL license.
63
    </xsd:documentation>
64
  </xsd:annotation>
65
66
  <xsd:annotation>
67
    <xsd:documentation>
68
69
      This is the XML Schema for the JSP 2.1 deployment descriptor
70
      types.  The JSP 2.1 schema contains all the special
71
      structures and datatypes that are necessary to use JSP files
72
      from a web application.
73
74
      The contents of this schema is used by the web-app_2_5.xsd
75
      file to define JSP specific content.
76
77
    </xsd:documentation>
78
  </xsd:annotation>
79
80
  <xsd:annotation>
81
    <xsd:documentation>
82
83
      The following conventions apply to all Java EE
84
      deployment descriptor elements unless indicated otherwise.
85
86
      - In elements that specify a pathname to a file within the
87
	same JAR file, relative filenames (i.e., those not
88
	starting with "/") are considered relative to the root of
89
	the JAR file's namespace.  Absolute filenames (i.e., those
90
	starting with "/") also specify names in the root of the
91
	JAR file's namespace.  In general, relative names are
92
	preferred.  The exception is .war files where absolute
93
	names are preferred for consistency with the Servlet API.
94
95
    </xsd:documentation>
96
  </xsd:annotation>
97
98
  <xsd:include schemaLocation="javaee_5.xsd"/>
99
100
101
<!-- **************************************************** -->
102
103
  <xsd:complexType name="jsp-configType">
104
    <xsd:annotation>
105
      <xsd:documentation>
106
107
	The jsp-configType is used to provide global configuration
108
	information for the JSP files in a web application. It has
109
	two subelements, taglib and jsp-property-group.
110
111
      </xsd:documentation>
112
    </xsd:annotation>
113
114
    <xsd:sequence>
115
      <xsd:element name="taglib"
116
		   type="javaee:taglibType"
117
		   minOccurs="0"
118
		   maxOccurs="unbounded"/>
119
      <xsd:element name="jsp-property-group"
120
		   type="javaee:jsp-property-groupType"
121
		   minOccurs="0"
122
		   maxOccurs="unbounded"/>
123
    </xsd:sequence>
124
    <xsd:attribute name="id" type="xsd:ID"/>
125
  </xsd:complexType>
126
127
<!-- **************************************************** -->
128
129
  <xsd:complexType name="jsp-fileType">
130
    <xsd:annotation>
131
      <xsd:documentation>
132
133
	The jsp-file element contains the full path to a JSP file
134
	within the web application beginning with a `/'.
135
136
      </xsd:documentation>
137
    </xsd:annotation>
138
139
    <xsd:simpleContent>
140
      <xsd:restriction base="javaee:pathType"/>
141
    </xsd:simpleContent>
142
  </xsd:complexType>
143
144
<!-- **************************************************** -->
145
146
  <xsd:complexType name="jsp-property-groupType">
147
    <xsd:annotation>
148
      <xsd:documentation>
149
150
	The jsp-property-groupType is used to group a number of
151
	files so they can be given global property information.
152
	All files so described are deemed to be JSP files.  The
153
	following additional properties can be described:
154
155
	    - Control whether EL is ignored.
156
	    - Control whether scripting elements are invalid.
157
	    - Indicate pageEncoding information.
158
	    - Indicate that a resource is a JSP document (XML).
159
	    - Prelude and Coda automatic includes.
160
            - Control whether the character sequence #{ is allowed
161
              when used as a String literal.
162
            - Control whether template text containing only
163
              whitespaces must be removed from the response output.
164
165
      </xsd:documentation>
166
    </xsd:annotation>
167
168
    <xsd:sequence>
169
      <xsd:group ref="javaee:descriptionGroup"/>
170
      <xsd:element name="url-pattern"
171
		   type="javaee:url-patternType"
172
		   maxOccurs="unbounded"/>
173
      <xsd:element name="el-ignored"
174
		   type="javaee:true-falseType"
175
		   minOccurs="0">
176
	<xsd:annotation>
177
	  <xsd:documentation>
178
179
	    Can be used to easily set the isELIgnored
180
	    property of a group of JSP pages.  By default, the
181
	    EL evaluation is enabled for Web Applications using
182
	    a Servlet 2.4 or greater web.xml, and disabled
183
	    otherwise.
184
185
	  </xsd:documentation>
186
	</xsd:annotation>
187
      </xsd:element>
188
      <xsd:element name="page-encoding"
189
		   type="javaee:string"
190
		   minOccurs="0">
191
	<xsd:annotation>
192
	  <xsd:documentation>
193
194
	    The valid values of page-encoding are those of the
195
	    pageEncoding page directive.  It is a
196
	    translation-time error to name different encodings
197
	    in the pageEncoding attribute of the page directive
198
	    of a JSP page and in a JSP configuration element
199
	    matching the page.  It is also a translation-time
200
	    error to name different encodings in the prolog
201
	    or text declaration of a document in XML syntax and
202
	    in a JSP configuration element matching the document.
203
	    It is legal to name the same encoding through
204
	    mulitple mechanisms.
205
206
	  </xsd:documentation>
207
	</xsd:annotation>
208
      </xsd:element>
209
      <xsd:element name="scripting-invalid"
210
		   type="javaee:true-falseType"
211
		   minOccurs="0">
212
	<xsd:annotation>
213
	  <xsd:documentation>
214
215
	    Can be used to easily disable scripting in a
216
	    group of JSP pages.  By default, scripting is
217
	    enabled.
218
219
	  </xsd:documentation>
220
	</xsd:annotation>
221
      </xsd:element>
222
      <xsd:element name="is-xml"
223
		   type="javaee:true-falseType"
224
		   minOccurs="0">
225
	<xsd:annotation>
226
	  <xsd:documentation>
227
228
	    If true, denotes that the group of resources
229
	    that match the URL pattern are JSP documents,
230
	    and thus must be interpreted as XML documents.
231
	    If false, the resources are assumed to not
232
	    be JSP documents, unless there is another
233
	    property group that indicates otherwise.
234
235
	  </xsd:documentation>
236
	</xsd:annotation>
237
      </xsd:element>
238
      <xsd:element name="include-prelude"
239
		   type="javaee:pathType"
240
		   minOccurs="0"
241
		   maxOccurs="unbounded">
242
	<xsd:annotation>
243
	  <xsd:documentation>
244
245
	    The include-prelude element is a context-relative
246
	    path that must correspond to an element in the
247
	    Web Application.  When the element is present,
248
	    the given path will be automatically included (as
249
	    in an include directive) at the beginning of each
250
	    JSP page in this jsp-property-group.
251
252
	  </xsd:documentation>
253
	</xsd:annotation>
254
      </xsd:element>
255
      <xsd:element name="include-coda"
256
		   type="javaee:pathType"
257
		   minOccurs="0"
258
		   maxOccurs="unbounded">
259
	<xsd:annotation>
260
	  <xsd:documentation>
261
262
	    The include-coda element is a context-relative
263
	    path that must correspond to an element in the
264
	    Web Application.  When the element is present,
265
	    the given path will be automatically included (as
266
	    in an include directive) at the end of each
267
	    JSP page in this jsp-property-group.
268
269
	  </xsd:documentation>
270
	</xsd:annotation>
271
      </xsd:element>
272
      <xsd:element name="deferred-syntax-allowed-as-literal"
273
		   type="javaee:true-falseType"
274
		   minOccurs="0">
275
	<xsd:annotation>
276
	  <xsd:documentation>
277
278
             The character sequence #{ is reserved for EL expressions.
279
             Consequently, a translation error occurs if the #{
280
             character sequence is used as a String literal, unless
281
             this element is enabled (true). Disabled (false) by
282
             default.
283
284
	  </xsd:documentation>
285
	</xsd:annotation>
286
      </xsd:element>
287
      <xsd:element name="trim-directive-whitespaces"
288
		   type="javaee:true-falseType"
289
		   minOccurs="0">
290
	<xsd:annotation>
291
	  <xsd:documentation>
292
293
             Indicates that template text containing only whitespaces
294
             must be removed from the response output. It has no
295
             effect on JSP documents (XML syntax). Disabled (false)
296
             by default.
297
298
	  </xsd:documentation>
299
	</xsd:annotation>
300
      </xsd:element>
301
    </xsd:sequence>
302
    <xsd:attribute name="id" type="xsd:ID"/>
303
  </xsd:complexType>
304
305
<!-- **************************************************** -->
306
307
  <xsd:complexType name="taglibType">
308
    <xsd:annotation>
309
      <xsd:documentation>
310
311
	The taglibType defines the syntax for declaring in
312
	the deployment descriptor that a tag library is
313
	available to the application.  This can be done
314
	to override implicit map entries from TLD files and
315
	from the container.
316
317
      </xsd:documentation>
318
    </xsd:annotation>
319
320
    <xsd:sequence>
321
      <xsd:element name="taglib-uri"
322
		   type="javaee:string">
323
	<xsd:annotation>
324
	  <xsd:documentation>
325
326
	    A taglib-uri element describes a URI identifying a
327
	    tag library used in the web application.  The body
328
	    of the taglib-uri element may be either an
329
	    absolute URI specification, or a relative URI.
330
	    There should be no entries in web.xml with the
331
	    same taglib-uri value.
332
333
	  </xsd:documentation>
334
	</xsd:annotation>
335
      </xsd:element>
336
337
      <xsd:element name="taglib-location"
338
		   type="javaee:pathType">
339
	<xsd:annotation>
340
	  <xsd:documentation>
341
342
	    the taglib-location element contains the location
343
	    (as a resource relative to the root of the web
344
	    application) where to find the Tag Library
345
	    Description file for the tag library.
346
347
	  </xsd:documentation>
348
	</xsd:annotation>
349
      </xsd:element>
350
351
    </xsd:sequence>
352
    <xsd:attribute name="id" type="xsd:ID"/>
353
  </xsd:complexType>
354
355
</xsd:schema>
356
(-)java/javax/servlet/resources/jsp_2_2.xsd (+396 lines)
Line 0 Link Here
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/javaee"
4
            xmlns:javaee="http://java.sun.com/xml/ns/javaee"
5
            xmlns:xsd="http://www.w3.org/2001/XMLSchema"
6
            elementFormDefault="qualified"
7
            attributeFormDefault="unqualified"
8
            version="2.2">
9
  <xsd:annotation>
10
    <xsd:documentation>
11
12
      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
13
      
14
      Copyright 2003-2009 Sun Microsystems, Inc. All rights reserved.
15
      
16
      The contents of this file are subject to the terms of either the
17
      GNU General Public License Version 2 only ("GPL") or the Common
18
      Development and Distribution License("CDDL") (collectively, the
19
      "License").  You may not use this file except in compliance with
20
      the License. You can obtain a copy of the License at
21
      https://glassfish.dev.java.net/public/CDDL+GPL.html or
22
      glassfish/bootstrap/legal/LICENSE.txt.  See the License for the
23
      specific language governing permissions and limitations under the
24
      License.
25
      
26
      When distributing the software, include this License Header
27
      Notice in each file and include the License file at
28
      glassfish/bootstrap/legal/LICENSE.txt.  Sun designates this
29
      particular file as subject to the "Classpath" exception as
30
      provided by Sun in the GPL Version 2 section of the License file
31
      that accompanied this code.  If applicable, add the following
32
      below the License Header, with the fields enclosed by brackets []
33
      replaced by your own identifying information:
34
      "Portions Copyrighted [year] [name of copyright owner]"
35
      
36
      Contributor(s):
37
      
38
      If you wish your version of this file to be governed by only the
39
      CDDL or only the GPL Version 2, indicate your decision by adding
40
      "[Contributor] elects to include this software in this
41
      distribution under the [CDDL or GPL Version 2] license."  If you
42
      don't indicate a single choice of license, a recipient has the
43
      option to distribute your version of this file under either the
44
      CDDL, the GPL Version 2 or to extend the choice of license to its
45
      licensees as provided above.  However, if you add GPL Version 2
46
      code and therefore, elected the GPL Version 2 license, then the
47
      option applies only if the new code is made subject to such
48
      option by the copyright holder.
49
      
50
    </xsd:documentation>
51
  </xsd:annotation>
52
53
  <xsd:annotation>
54
    <xsd:documentation>
55
      The Apache Software Foundation elects to include this software under the
56
      CDDL license.
57
    </xsd:documentation>
58
  </xsd:annotation>
59
60
  <xsd:annotation>
61
    <xsd:documentation>
62
63
      This is the XML Schema for the JSP 2.2 deployment descriptor
64
      types.  The JSP 2.2 schema contains all the special
65
      structures and datatypes that are necessary to use JSP files
66
      from a web application. 
67
      
68
      The contents of this schema is used by the web-common_3_0.xsd 
69
      file to define JSP specific content. 
70
      
71
    </xsd:documentation>
72
  </xsd:annotation>
73
74
  <xsd:annotation>
75
    <xsd:documentation>
76
77
      The following conventions apply to all Java EE
78
      deployment descriptor elements unless indicated otherwise.
79
      
80
      - In elements that specify a pathname to a file within the
81
      same JAR file, relative filenames (i.e., those not
82
      starting with "/") are considered relative to the root of
83
      the JAR file's namespace.  Absolute filenames (i.e., those
84
      starting with "/") also specify names in the root of the
85
      JAR file's namespace.  In general, relative names are
86
      preferred.  The exception is .war files where absolute
87
      names are preferred for consistency with the Servlet API.
88
      
89
    </xsd:documentation>
90
  </xsd:annotation>
91
92
  <xsd:include schemaLocation="javaee_6.xsd"/>
93
94
95
<!-- **************************************************** -->
96
97
  <xsd:complexType name="jsp-configType">
98
    <xsd:annotation>
99
      <xsd:documentation>
100
101
        The jsp-configType is used to provide global configuration
102
        information for the JSP files in a web application. It has
103
        two subelements, taglib and jsp-property-group.
104
        
105
      </xsd:documentation>
106
    </xsd:annotation>
107
    <xsd:sequence>
108
      <xsd:element name="taglib"
109
                   type="javaee:taglibType"
110
                   minOccurs="0"
111
                   maxOccurs="unbounded"/>
112
      <xsd:element name="jsp-property-group"
113
                   type="javaee:jsp-property-groupType"
114
                   minOccurs="0"
115
                   maxOccurs="unbounded"/>
116
    </xsd:sequence>
117
    <xsd:attribute name="id"
118
                   type="xsd:ID"/>
119
  </xsd:complexType>
120
121
122
<!-- **************************************************** -->
123
124
  <xsd:complexType name="jsp-fileType">
125
    <xsd:annotation>
126
      <xsd:documentation>
127
128
        The jsp-file element contains the full path to a JSP file
129
        within the web application beginning with a `/'.
130
        
131
      </xsd:documentation>
132
    </xsd:annotation>
133
    <xsd:simpleContent>
134
      <xsd:restriction base="javaee:pathType"/>
135
    </xsd:simpleContent>
136
  </xsd:complexType>
137
138
139
<!-- **************************************************** -->
140
141
  <xsd:complexType name="jsp-property-groupType">
142
    <xsd:annotation>
143
      <xsd:documentation>
144
145
        The jsp-property-groupType is used to group a number of
146
        files so they can be given global property information.
147
        All files so described are deemed to be JSP files.  The
148
        following additional properties can be described:
149
        
150
        - Control whether EL is ignored.
151
        - Control whether scripting elements are invalid.
152
        - Indicate pageEncoding information.
153
        - Indicate that a resource is a JSP document (XML).
154
        - Prelude and Coda automatic includes.
155
        - Control whether the character sequence #{ is allowed
156
        when used as a String literal.
157
        - Control whether template text containing only
158
        whitespaces must be removed from the response output.
159
        - Indicate the default contentType information.
160
        - Indicate the default buffering model for JspWriter
161
        - Control whether error should be raised for the use of
162
        undeclared namespaces in a JSP page.
163
        
164
      </xsd:documentation>
165
    </xsd:annotation>
166
    <xsd:sequence>
167
      <xsd:group ref="javaee:descriptionGroup"/>
168
      <xsd:element name="url-pattern"
169
                   type="javaee:url-patternType"
170
                   maxOccurs="unbounded"/>
171
      <xsd:element name="el-ignored"
172
                   type="javaee:true-falseType"
173
                   minOccurs="0">
174
        <xsd:annotation>
175
          <xsd:documentation>
176
177
            Can be used to easily set the isELIgnored
178
            property of a group of JSP pages.  By default, the
179
            EL evaluation is enabled for Web Applications using
180
            a Servlet 2.4 or greater web.xml, and disabled
181
            otherwise.
182
            
183
          </xsd:documentation>
184
        </xsd:annotation>
185
      </xsd:element>
186
      <xsd:element name="page-encoding"
187
                   type="javaee:string"
188
                   minOccurs="0">
189
        <xsd:annotation>
190
          <xsd:documentation>
191
192
            The valid values of page-encoding are those of the
193
            pageEncoding page directive.  It is a
194
            translation-time error to name different encodings
195
            in the pageEncoding attribute of the page directive
196
            of a JSP page and in a JSP configuration element
197
            matching the page.  It is also a translation-time
198
            error to name different encodings in the prolog
199
            or text declaration of a document in XML syntax and
200
            in a JSP configuration element matching the document.
201
            It is legal to name the same encoding through
202
            mulitple mechanisms.
203
            
204
          </xsd:documentation>
205
        </xsd:annotation>
206
      </xsd:element>
207
      <xsd:element name="scripting-invalid"
208
                   type="javaee:true-falseType"
209
                   minOccurs="0">
210
        <xsd:annotation>
211
          <xsd:documentation>
212
213
            Can be used to easily disable scripting in a
214
            group of JSP pages.  By default, scripting is
215
            enabled.
216
            
217
          </xsd:documentation>
218
        </xsd:annotation>
219
      </xsd:element>
220
      <xsd:element name="is-xml"
221
                   type="javaee:true-falseType"
222
                   minOccurs="0">
223
        <xsd:annotation>
224
          <xsd:documentation>
225
226
            If true, denotes that the group of resources
227
            that match the URL pattern are JSP documents,
228
            and thus must be interpreted as XML documents.
229
            If false, the resources are assumed to not
230
            be JSP documents, unless there is another
231
            property group that indicates otherwise.
232
            
233
          </xsd:documentation>
234
        </xsd:annotation>
235
      </xsd:element>
236
      <xsd:element name="include-prelude"
237
                   type="javaee:pathType"
238
                   minOccurs="0"
239
                   maxOccurs="unbounded">
240
        <xsd:annotation>
241
          <xsd:documentation>
242
243
            The include-prelude element is a context-relative
244
            path that must correspond to an element in the
245
            Web Application.  When the element is present,
246
            the given path will be automatically included (as
247
            in an include directive) at the beginning of each
248
            JSP page in this jsp-property-group.
249
            
250
          </xsd:documentation>
251
        </xsd:annotation>
252
      </xsd:element>
253
      <xsd:element name="include-coda"
254
                   type="javaee:pathType"
255
                   minOccurs="0"
256
                   maxOccurs="unbounded">
257
        <xsd:annotation>
258
          <xsd:documentation>
259
260
            The include-coda element is a context-relative
261
            path that must correspond to an element in the
262
            Web Application.  When the element is present,
263
            the given path will be automatically included (as
264
            in an include directive) at the end of each
265
            JSP page in this jsp-property-group.
266
            
267
          </xsd:documentation>
268
        </xsd:annotation>
269
      </xsd:element>
270
      <xsd:element name="deferred-syntax-allowed-as-literal"
271
                   type="javaee:true-falseType"
272
                   minOccurs="0">
273
        <xsd:annotation>
274
          <xsd:documentation>
275
276
            The character sequence #{ is reserved for EL expressions.
277
            Consequently, a translation error occurs if the #{
278
            character sequence is used as a String literal, unless
279
            this element is enabled (true). Disabled (false) by
280
            default.
281
            
282
          </xsd:documentation>
283
        </xsd:annotation>
284
      </xsd:element>
285
      <xsd:element name="trim-directive-whitespaces"
286
                   type="javaee:true-falseType"
287
                   minOccurs="0">
288
        <xsd:annotation>
289
          <xsd:documentation>
290
291
            Indicates that template text containing only whitespaces
292
            must be removed from the response output. It has no
293
            effect on JSP documents (XML syntax). Disabled (false)
294
            by default.
295
            
296
          </xsd:documentation>
297
        </xsd:annotation>
298
      </xsd:element>
299
      <xsd:element name="default-content-type"
300
                   type="javaee:string"
301
                   minOccurs="0">
302
        <xsd:annotation>
303
          <xsd:documentation>
304
305
            The valid values of default-content-type are those of the
306
            contentType page directive.  It specifies the default
307
            response contentType if the page directive does not include
308
            a contentType attribute.
309
            
310
          </xsd:documentation>
311
        </xsd:annotation>
312
      </xsd:element>
313
      <xsd:element name="buffer"
314
                   type="javaee:string"
315
                   minOccurs="0">
316
        <xsd:annotation>
317
          <xsd:documentation>
318
319
            The valid values of buffer are those of the
320
            buffer page directive.  It specifies if buffering should be
321
            used for the output to response, and if so, the size of the
322
            buffer to use.
323
            
324
          </xsd:documentation>
325
        </xsd:annotation>
326
      </xsd:element>
327
      <xsd:element name="error-on-undeclared-namespace"
328
                   type="javaee:true-falseType"
329
                   minOccurs="0">
330
        <xsd:annotation>
331
          <xsd:documentation>
332
333
            The default behavior when a tag with unknown namespace is used
334
            in a JSP page (regular syntax) is to silently ignore it.  If
335
            set to true, then an error must be raised during the translation
336
            time when an undeclared tag is used in a JSP page.  Disabled
337
            (false) by default.
338
            
339
          </xsd:documentation>
340
        </xsd:annotation>
341
      </xsd:element>
342
    </xsd:sequence>
343
    <xsd:attribute name="id"
344
                   type="xsd:ID"/>
345
  </xsd:complexType>
346
347
348
<!-- **************************************************** -->
349
350
  <xsd:complexType name="taglibType">
351
    <xsd:annotation>
352
      <xsd:documentation>
353
354
        The taglibType defines the syntax for declaring in
355
        the deployment descriptor that a tag library is
356
        available to the application.  This can be done
357
        to override implicit map entries from TLD files and
358
        from the container.
359
        
360
      </xsd:documentation>
361
    </xsd:annotation>
362
    <xsd:sequence>
363
      <xsd:element name="taglib-uri"
364
                   type="javaee:string">
365
        <xsd:annotation>
366
          <xsd:documentation>
367
368
            A taglib-uri element describes a URI identifying a
369
            tag library used in the web application.  The body
370
            of the taglib-uri element may be either an
371
            absolute URI specification, or a relative URI.
372
            There should be no entries in web.xml with the
373
            same taglib-uri value.
374
            
375
          </xsd:documentation>
376
        </xsd:annotation>
377
      </xsd:element>
378
      <xsd:element name="taglib-location"
379
                   type="javaee:pathType">
380
        <xsd:annotation>
381
          <xsd:documentation>
382
383
            the taglib-location element contains the location
384
            (as a resource relative to the root of the web
385
            application) where to find the Tag Library
386
            Description file for the tag library.
387
            
388
          </xsd:documentation>
389
        </xsd:annotation>
390
      </xsd:element>
391
    </xsd:sequence>
392
    <xsd:attribute name="id"
393
                   type="xsd:ID"/>
394
  </xsd:complexType>
395
396
</xsd:schema>
(-)java/javax/servlet/resources/jsp_2_3.xsd (+396 lines)
Line 0 Link Here
1
<?xml version="1.0" encoding="UTF-8"?>
2
<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
3
            targetNamespace="http://xmlns.jcp.org/xml/ns/javaee"
4
            xmlns:javaee="http://xmlns.jcp.org/xml/ns/javaee"
5
            xmlns:xsd="http://www.w3.org/2001/XMLSchema"
6
            elementFormDefault="qualified"
7
            attributeFormDefault="unqualified"
8
            version="2.3">
9
  <xsd:annotation>
10
    <xsd:documentation>
11
12
      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
13
      
14
      Copyright (c) 2009-2013 Oracle and/or its affiliates. All rights reserved.
15
      
16
      The contents of this file are subject to the terms of either the GNU
17
      General Public License Version 2 only ("GPL") or the Common Development
18
      and Distribution License("CDDL") (collectively, the "License").  You
19
      may not use this file except in compliance with the License.  You can
20
      obtain a copy of the License at
21
      https://glassfish.dev.java.net/public/CDDL+GPL_1_1.html
22
      or packager/legal/LICENSE.txt.  See the License for the specific
23
      language governing permissions and limitations under the License.
24
      
25
      When distributing the software, include this License Header Notice in each
26
      file and include the License file at packager/legal/LICENSE.txt.
27
      
28
      GPL Classpath Exception:
29
      Oracle designates this particular file as subject to the "Classpath"
30
      exception as provided by Oracle in the GPL Version 2 section of the License
31
      file that accompanied this code.
32
      
33
      Modifications:
34
      If applicable, add the following below the License Header, with the fields
35
      enclosed by brackets [] replaced by your own identifying information:
36
      "Portions Copyright [year] [name of copyright owner]"
37
      
38
      Contributor(s):
39
      If you wish your version of this file to be governed by only the CDDL or
40
      only the GPL Version 2, indicate your decision by adding "[Contributor]
41
      elects to include this software in this distribution under the [CDDL or GPL
42
      Version 2] license."  If you don't indicate a single choice of license, a
43
      recipient has the option to distribute your version of this file under
44
      either the CDDL, the GPL Version 2 or to extend the choice of license to
45
      its licensees as provided above.  However, if you add GPL Version 2 code
46
      and therefore, elected the GPL Version 2 license, then the option applies
47
      only if the new code is made subject to such option by the copyright
48
      holder.
49
      
50
    </xsd:documentation>
51
  </xsd:annotation>
52
53
  <xsd:annotation>
54
    <xsd:documentation>
55
      The Apache Software Foundation elects to include this software under the
56
      CDDL license.
57
    </xsd:documentation>
58
  </xsd:annotation>
59
60
  <xsd:annotation>
61
    <xsd:documentation>
62
63
      This is the XML Schema for the JSP 2.3 deployment descriptor
64
      types.  The JSP 2.3 schema contains all the special
65
      structures and datatypes that are necessary to use JSP files
66
      from a web application. 
67
      
68
      The contents of this schema is used by the web-common_3_1.xsd 
69
      file to define JSP specific content. 
70
      
71
    </xsd:documentation>
72
  </xsd:annotation>
73
74
  <xsd:annotation>
75
    <xsd:documentation>
76
77
      The following conventions apply to all Java EE
78
      deployment descriptor elements unless indicated otherwise.
79
      
80
      - In elements that specify a pathname to a file within the
81
      same JAR file, relative filenames (i.e., those not
82
      starting with "/") are considered relative to the root of
83
      the JAR file's namespace.  Absolute filenames (i.e., those
84
      starting with "/") also specify names in the root of the
85
      JAR file's namespace.  In general, relative names are
86
      preferred.  The exception is .war files where absolute
87
      names are preferred for consistency with the Servlet API.
88
      
89
    </xsd:documentation>
90
  </xsd:annotation>
91
92
  <xsd:include schemaLocation="javaee_7.xsd"/>
93
94
95
<!-- **************************************************** -->
96
97
  <xsd:complexType name="jsp-configType">
98
    <xsd:annotation>
99
      <xsd:documentation>
100
101
        The jsp-configType is used to provide global configuration
102
        information for the JSP files in a web application. It has
103
        two subelements, taglib and jsp-property-group.
104
        
105
      </xsd:documentation>
106
    </xsd:annotation>
107
    <xsd:sequence>
108
      <xsd:element name="taglib"
109
                   type="javaee:taglibType"
110
                   minOccurs="0"
111
                   maxOccurs="unbounded"/>
112
      <xsd:element name="jsp-property-group"
113
                   type="javaee:jsp-property-groupType"
114
                   minOccurs="0"
115
                   maxOccurs="unbounded"/>
116
    </xsd:sequence>
117
    <xsd:attribute name="id"
118
                   type="xsd:ID"/>
119
  </xsd:complexType>
120
121
122
<!-- **************************************************** -->
123
124
  <xsd:complexType name="jsp-fileType">
125
    <xsd:annotation>
126
      <xsd:documentation>
127
128
        The jsp-file element contains the full path to a JSP file
129
        within the web application beginning with a `/'.
130
        
131
      </xsd:documentation>
132
    </xsd:annotation>
133
    <xsd:simpleContent>
134
      <xsd:restriction base="javaee:pathType"/>
135
    </xsd:simpleContent>
136
  </xsd:complexType>
137
138
139
<!-- **************************************************** -->
140
141
  <xsd:complexType name="jsp-property-groupType">
142
    <xsd:annotation>
143
      <xsd:documentation>
144
145
        The jsp-property-groupType is used to group a number of
146
        files so they can be given global property information.
147
        All files so described are deemed to be JSP files.  The
148
        following additional properties can be described:
149
        
150
        - Control whether EL is ignored.
151
        - Control whether scripting elements are invalid.
152
        - Indicate pageEncoding information.
153
        - Indicate that a resource is a JSP document (XML).
154
        - Prelude and Coda automatic includes.
155
        - Control whether the character sequence #{ is allowed
156
        when used as a String literal.
157
        - Control whether template text containing only
158
        whitespaces must be removed from the response output.
159
        - Indicate the default contentType information.
160
        - Indicate the default buffering model for JspWriter
161
        - Control whether error should be raised for the use of
162
        undeclared namespaces in a JSP page.
163
        
164
      </xsd:documentation>
165
    </xsd:annotation>
166
    <xsd:sequence>
167
      <xsd:group ref="javaee:descriptionGroup"/>
168
      <xsd:element name="url-pattern"
169
                   type="javaee:url-patternType"
170
                   maxOccurs="unbounded"/>
171
      <xsd:element name="el-ignored"
172
                   type="javaee:true-falseType"
173
                   minOccurs="0">
174
        <xsd:annotation>
175
          <xsd:documentation>
176
177
            Can be used to easily set the isELIgnored
178
            property of a group of JSP pages.  By default, the
179
            EL evaluation is enabled for Web Applications using
180
            a Servlet 2.4 or greater web.xml, and disabled
181
            otherwise.
182
            
183
          </xsd:documentation>
184
        </xsd:annotation>
185
      </xsd:element>
186
      <xsd:element name="page-encoding"
187
                   type="javaee:string"
188
                   minOccurs="0">
189
        <xsd:annotation>
190
          <xsd:documentation>
191
192
            The valid values of page-encoding are those of the
193
            pageEncoding page directive.  It is a
194
            translation-time error to name different encodings
195
            in the pageEncoding attribute of the page directive
196
            of a JSP page and in a JSP configuration element
197
            matching the page.  It is also a translation-time
198
            error to name different encodings in the prolog
199
            or text declaration of a document in XML syntax and
200
            in a JSP configuration element matching the document.
201
            It is legal to name the same encoding through
202
            mulitple mechanisms.
203
            
204
          </xsd:documentation>
205
        </xsd:annotation>
206
      </xsd:element>
207
      <xsd:element name="scripting-invalid"
208
                   type="javaee:true-falseType"
209
                   minOccurs="0">
210
        <xsd:annotation>
211
          <xsd:documentation>
212
213
            Can be used to easily disable scripting in a
214
            group of JSP pages.  By default, scripting is
215
            enabled.
216
            
217
          </xsd:documentation>
218
        </xsd:annotation>
219
      </xsd:element>
220
      <xsd:element name="is-xml"
221
                   type="javaee:true-falseType"
222
                   minOccurs="0">
223
        <xsd:annotation>
224
          <xsd:documentation>
225
226
            If true, denotes that the group of resources
227
            that match the URL pattern are JSP documents,
228
            and thus must be interpreted as XML documents.
229
            If false, the resources are assumed to not
230
            be JSP documents, unless there is another
231
            property group that indicates otherwise.
232
            
233
          </xsd:documentation>
234
        </xsd:annotation>
235
      </xsd:element>
236
      <xsd:element name="include-prelude"
237
                   type="javaee:pathType"
238
                   minOccurs="0"
239
                   maxOccurs="unbounded">
240
        <xsd:annotation>
241
          <xsd:documentation>
242
243
            The include-prelude element is a context-relative
244
            path that must correspond to an element in the
245
            Web Application.  When the element is present,
246
            the given path will be automatically included (as
247
            in an include directive) at the beginning of each
248
            JSP page in this jsp-property-group.
249
            
250
          </xsd:documentation>
251
        </xsd:annotation>
252
      </xsd:element>
253
      <xsd:element name="include-coda"
254
                   type="javaee:pathType"
255
                   minOccurs="0"
256
                   maxOccurs="unbounded">
257
        <xsd:annotation>
258
          <xsd:documentation>
259
260
            The include-coda element is a context-relative
261
            path that must correspond to an element in the
262
            Web Application.  When the element is present,
263
            the given path will be automatically included (as
264
            in an include directive) at the end of each
265
            JSP page in this jsp-property-group.
266
            
267
          </xsd:documentation>
268
        </xsd:annotation>
269
      </xsd:element>
270
      <xsd:element name="deferred-syntax-allowed-as-literal"
271
                   type="javaee:true-falseType"
272
                   minOccurs="0">
273
        <xsd:annotation>
274
          <xsd:documentation>
275
276
            The character sequence #{ is reserved for EL expressions.
277
            Consequently, a translation error occurs if the #{
278
            character sequence is used as a String literal, unless
279
            this element is enabled (true). Disabled (false) by
280
            default.
281
            
282
          </xsd:documentation>
283
        </xsd:annotation>
284
      </xsd:element>
285
      <xsd:element name="trim-directive-whitespaces"
286
                   type="javaee:true-falseType"
287
                   minOccurs="0">
288
        <xsd:annotation>
289
          <xsd:documentation>
290
291
            Indicates that template text containing only whitespaces
292
            must be removed from the response output. It has no
293
            effect on JSP documents (XML syntax). Disabled (false)
294
            by default.
295
            
296
          </xsd:documentation>
297
        </xsd:annotation>
298
      </xsd:element>
299
      <xsd:element name="default-content-type"
300
                   type="javaee:string"
301
                   minOccurs="0">
302
        <xsd:annotation>
303
          <xsd:documentation>
304
305
            The valid values of default-content-type are those of the
306
            contentType page directive.  It specifies the default
307
            response contentType if the page directive does not include
308
            a contentType attribute.
309
            
310
          </xsd:documentation>
311
        </xsd:annotation>
312
      </xsd:element>
313
      <xsd:element name="buffer"
314
                   type="javaee:string"
315
                   minOccurs="0">
316
        <xsd:annotation>
317
          <xsd:documentation>
318
319
            The valid values of buffer are those of the
320
            buffer page directive.  It specifies if buffering should be
321
            used for the output to response, and if so, the size of the
322
            buffer to use.
323
            
324
          </xsd:documentation>
325
        </xsd:annotation>
326
      </xsd:element>
327
      <xsd:element name="error-on-undeclared-namespace"
328
                   type="javaee:true-falseType"
329
                   minOccurs="0">
330
        <xsd:annotation>
331
          <xsd:documentation>
332
333
            The default behavior when a tag with unknown namespace is used
334
            in a JSP page (regular syntax) is to silently ignore it.  If
335
            set to true, then an error must be raised during the translation
336
            time when an undeclared tag is used in a JSP page.  Disabled
337
            (false) by default.
338
            
339
          </xsd:documentation>
340
        </xsd:annotation>
341
      </xsd:element>
342
    </xsd:sequence>
343
    <xsd:attribute name="id"
344
                   type="xsd:ID"/>
345
  </xsd:complexType>
346
347
348
<!-- **************************************************** -->
349
350
  <xsd:complexType name="taglibType">
351
    <xsd:annotation>
352
      <xsd:documentation>
353
354
        The taglibType defines the syntax for declaring in
355
        the deployment descriptor that a tag library is
356
        available to the application.  This can be done
357
        to override implicit map entries from TLD files and
358
        from the container.
359
        
360
      </xsd:documentation>
361
    </xsd:annotation>
362
    <xsd:sequence>
363
      <xsd:element name="taglib-uri"
364
                   type="javaee:string">
365
        <xsd:annotation>
366
          <xsd:documentation>
367
368
            A taglib-uri element describes a URI identifying a
369
            tag library used in the web application.  The body
370
            of the taglib-uri element may be either an
371
            absolute URI specification, or a relative URI.
372
            There should be no entries in web.xml with the
373
            same taglib-uri value.
374
            
375
          </xsd:documentation>
376
        </xsd:annotation>
377
      </xsd:element>
378
      <xsd:element name="taglib-location"
379
                   type="javaee:pathType">
380
        <xsd:annotation>
381
          <xsd:documentation>
382
383
            the taglib-location element contains the location
384
            (as a resource relative to the root of the web
385
            application) where to find the Tag Library
386
            Description file for the tag library.
387
            
388
          </xsd:documentation>
389
        </xsd:annotation>
390
      </xsd:element>
391
    </xsd:sequence>
392
    <xsd:attribute name="id"
393
                   type="xsd:ID"/>
394
  </xsd:complexType>
395
396
</xsd:schema>

Return to bug 55166