david_williams | e073de1 | 2007-04-28 04:01:44 +0000 | [diff] [blame] | 1 | <?xml version="1.0" encoding="UTF-8"?> |
| 2 | |
| 3 | <xsd:schema xmlns="http://www.w3.org/2001/XMLSchema" |
| 4 | targetNamespace="http://java.sun.com/xml/ns/j2ee" |
| 5 | xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" |
| 6 | xmlns:xsd="http://www.w3.org/2001/XMLSchema" |
| 7 | elementFormDefault="qualified" |
| 8 | attributeFormDefault="unqualified" |
| 9 | version="2.0"> |
| 10 | <xsd:annotation> |
| 11 | <xsd:documentation> |
| 12 | @(#)jsp_2_0.xsds 1.17 03/18/03 |
| 13 | </xsd:documentation> |
| 14 | </xsd:annotation> |
| 15 | |
| 16 | <xsd:annotation> |
| 17 | <xsd:documentation> |
| 18 | |
| 19 | Copyright 2003 Sun Microsystems, Inc., 901 San Antonio |
| 20 | Road, Palo Alto, California 94303, U.S.A. All rights |
| 21 | reserved. |
| 22 | |
| 23 | Sun Microsystems, Inc. has intellectual property rights |
| 24 | relating to technology described in this document. In |
| 25 | particular, and without limitation, these intellectual |
| 26 | property rights may include one or more of the U.S. patents |
| 27 | listed at http://www.sun.com/patents and one or more |
| 28 | additional patents or pending patent applications in the |
| 29 | U.S. and other countries. |
| 30 | |
| 31 | This document and the technology which it describes are |
| 32 | distributed under licenses restricting their use, copying, |
| 33 | distribution, and decompilation. No part of this document |
| 34 | may be reproduced in any form by any means without prior |
| 35 | written authorization of Sun and its licensors, if any. |
| 36 | |
| 37 | Third-party software, including font technology, is |
| 38 | copyrighted and licensed from Sun suppliers. |
| 39 | |
| 40 | Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE, |
| 41 | JavaServer Pages, Enterprise JavaBeans and the Java Coffee |
| 42 | Cup logo are trademarks or registered trademarks of Sun |
| 43 | Microsystems, Inc. in the U.S. and other countries. |
| 44 | |
| 45 | Federal Acquisitions: Commercial Software - Government Users |
| 46 | Subject to Standard License Terms and Conditions. |
| 47 | |
| 48 | </xsd:documentation> |
| 49 | </xsd:annotation> |
| 50 | |
| 51 | <xsd:annotation> |
| 52 | <xsd:documentation> |
| 53 | |
| 54 | This is the XML Schema for the JSP 2.0 deployment descriptor |
| 55 | types. The JSP 2.0 schema contains all the special |
| 56 | structures and datatypes that are necessary to use JSP files |
| 57 | from a web application. |
| 58 | |
| 59 | The contents of this schema is used by the web-app_2_4.xsd |
| 60 | file to define JSP specific content. |
| 61 | |
| 62 | </xsd:documentation> |
| 63 | </xsd:annotation> |
| 64 | |
| 65 | <xsd:annotation> |
| 66 | <xsd:documentation> |
| 67 | |
| 68 | The following conventions apply to all J2EE |
| 69 | deployment descriptor elements unless indicated otherwise. |
| 70 | |
| 71 | - In elements that specify a pathname to a file within the |
| 72 | same JAR file, relative filenames (i.e., those not |
| 73 | starting with "/") are considered relative to the root of |
| 74 | the JAR file's namespace. Absolute filenames (i.e., those |
| 75 | starting with "/") also specify names in the root of the |
| 76 | JAR file's namespace. In general, relative names are |
| 77 | preferred. The exception is .war files where absolute |
| 78 | names are preferred for consistency with the Servlet API. |
| 79 | |
| 80 | </xsd:documentation> |
| 81 | </xsd:annotation> |
| 82 | |
| 83 | <xsd:include schemaLocation="j2ee_1_4.xsd"/> |
| 84 | |
| 85 | |
| 86 | <!-- **************************************************** --> |
| 87 | |
| 88 | <xsd:complexType name="jsp-configType"> |
| 89 | <xsd:annotation> |
| 90 | <xsd:documentation> |
| 91 | |
| 92 | The jsp-configType is used to provide global configuration |
| 93 | information for the JSP files in a web application. It has |
| 94 | two subelements, taglib and jsp-property-group. |
| 95 | |
| 96 | </xsd:documentation> |
| 97 | </xsd:annotation> |
| 98 | |
| 99 | <xsd:sequence> |
| 100 | <xsd:element name="taglib" |
| 101 | type="j2ee:taglibType" |
| 102 | minOccurs="0" |
| 103 | maxOccurs="unbounded"/> |
| 104 | <xsd:element name="jsp-property-group" |
| 105 | type="j2ee:jsp-property-groupType" |
| 106 | minOccurs="0" |
| 107 | maxOccurs="unbounded"/> |
| 108 | </xsd:sequence> |
| 109 | <xsd:attribute name="id" type="xsd:ID"/> |
| 110 | </xsd:complexType> |
| 111 | |
| 112 | <!-- **************************************************** --> |
| 113 | |
| 114 | <xsd:complexType name="jsp-fileType"> |
| 115 | <xsd:annotation> |
| 116 | <xsd:documentation> |
| 117 | |
| 118 | The jsp-file element contains the full path to a JSP file |
| 119 | within the web application beginning with a `/'. |
| 120 | |
| 121 | </xsd:documentation> |
| 122 | </xsd:annotation> |
| 123 | |
| 124 | <xsd:simpleContent> |
| 125 | <xsd:restriction base="j2ee:pathType"/> |
| 126 | </xsd:simpleContent> |
| 127 | </xsd:complexType> |
| 128 | |
| 129 | <!-- **************************************************** --> |
| 130 | |
| 131 | <xsd:complexType name="jsp-property-groupType"> |
| 132 | <xsd:annotation> |
| 133 | <xsd:documentation> |
| 134 | |
| 135 | The jsp-property-groupType is used to group a number of |
| 136 | files so they can be given global property information. |
| 137 | All files so described are deemed to be JSP files. The |
| 138 | following additional properties can be described: |
| 139 | |
| 140 | - Control whether EL is ignored |
| 141 | - Control whether scripting elements are invalid |
| 142 | - Indicate pageEncoding information. |
| 143 | - Indicate that a resource is a JSP document (XML) |
| 144 | - Prelude and Coda automatic includes. |
| 145 | |
| 146 | </xsd:documentation> |
| 147 | </xsd:annotation> |
| 148 | |
| 149 | <xsd:sequence> |
| 150 | <xsd:group ref="j2ee:descriptionGroup"/> |
| 151 | <xsd:element name="url-pattern" |
| 152 | type="j2ee:url-patternType" |
| 153 | maxOccurs="unbounded"/> |
| 154 | <xsd:element name="el-ignored" |
| 155 | type="j2ee:true-falseType" |
| 156 | minOccurs="0"> |
| 157 | <xsd:annotation> |
| 158 | <xsd:documentation> |
| 159 | |
| 160 | Can be used to easily set the isELIgnored |
| 161 | property of a group of JSP pages. By default, the |
| 162 | EL evaluation is enabled for Web Applications using |
| 163 | a Servlet 2.4 or greater web.xml, and disabled |
| 164 | otherwise. |
| 165 | |
| 166 | </xsd:documentation> |
| 167 | </xsd:annotation> |
| 168 | </xsd:element> |
| 169 | <xsd:element name="page-encoding" |
| 170 | type="j2ee:string" |
| 171 | minOccurs="0"> |
| 172 | <xsd:annotation> |
| 173 | <xsd:documentation> |
| 174 | |
| 175 | The valid values of page-encoding are those of the |
| 176 | pageEncoding page directive. It is a |
| 177 | translation-time error to name different encodings |
| 178 | in the pageEncoding attribute of the page directive |
| 179 | of a JSP page and in a JSP configuration element |
| 180 | matching the page. It is also a translation-time |
| 181 | error to name different encodings in the prolog |
| 182 | or text declaration of a document in XML syntax and |
| 183 | in a JSP configuration element matching the document. |
| 184 | It is legal to name the same encoding through |
| 185 | mulitple mechanisms. |
| 186 | |
| 187 | </xsd:documentation> |
| 188 | </xsd:annotation> |
| 189 | </xsd:element> |
| 190 | <xsd:element name="scripting-invalid" |
| 191 | type="j2ee:true-falseType" |
| 192 | minOccurs="0"> |
| 193 | <xsd:annotation> |
| 194 | <xsd:documentation> |
| 195 | |
| 196 | Can be used to easily disable scripting in a |
| 197 | group of JSP pages. By default, scripting is |
| 198 | enabled. |
| 199 | |
| 200 | </xsd:documentation> |
| 201 | </xsd:annotation> |
| 202 | </xsd:element> |
| 203 | <xsd:element name="is-xml" |
| 204 | type="j2ee:true-falseType" |
| 205 | minOccurs="0"> |
| 206 | <xsd:annotation> |
| 207 | <xsd:documentation> |
| 208 | |
| 209 | If true, denotes that the group of resources |
| 210 | that match the URL pattern are JSP documents, |
| 211 | and thus must be interpreted as XML documents. |
| 212 | If false, the resources are assumed to not |
| 213 | be JSP documents, unless there is another |
| 214 | property group that indicates otherwise. |
| 215 | |
| 216 | </xsd:documentation> |
| 217 | </xsd:annotation> |
| 218 | </xsd:element> |
| 219 | <xsd:element name="include-prelude" |
| 220 | type="j2ee:pathType" |
| 221 | minOccurs="0" |
| 222 | maxOccurs="unbounded"> |
| 223 | <xsd:annotation> |
| 224 | <xsd:documentation> |
| 225 | |
| 226 | The include-prelude element is a context-relative |
| 227 | path that must correspond to an element in the |
| 228 | Web Application. When the element is present, |
| 229 | the given path will be automatically included (as |
| 230 | in an include directive) at the beginning of each |
| 231 | JSP page in this jsp-property-group. |
| 232 | |
| 233 | </xsd:documentation> |
| 234 | </xsd:annotation> |
| 235 | </xsd:element> |
| 236 | <xsd:element name="include-coda" |
| 237 | type="j2ee:pathType" |
| 238 | minOccurs="0" |
| 239 | maxOccurs="unbounded"> |
| 240 | <xsd:annotation> |
| 241 | <xsd:documentation> |
| 242 | |
| 243 | The include-coda 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 end of each |
| 248 | JSP page in this jsp-property-group. |
| 249 | |
| 250 | </xsd:documentation> |
| 251 | </xsd:annotation> |
| 252 | </xsd:element> |
| 253 | </xsd:sequence> |
| 254 | <xsd:attribute name="id" type="xsd:ID"/> |
| 255 | </xsd:complexType> |
| 256 | |
| 257 | <!-- **************************************************** --> |
| 258 | |
| 259 | <xsd:complexType name="taglibType"> |
| 260 | <xsd:annotation> |
| 261 | <xsd:documentation> |
| 262 | |
| 263 | The taglibType defines the syntax for declaring in |
| 264 | the deployment descriptor that a tag library is |
| 265 | available to the application. This can be done |
| 266 | to override implicit map entries from TLD files and |
| 267 | from the container. |
| 268 | |
| 269 | </xsd:documentation> |
| 270 | </xsd:annotation> |
| 271 | |
| 272 | <xsd:sequence> |
| 273 | <xsd:element name="taglib-uri" |
| 274 | type="j2ee:string"> |
| 275 | <xsd:annotation> |
| 276 | <xsd:documentation> |
| 277 | |
| 278 | A taglib-uri element describes a URI identifying a |
| 279 | tag library used in the web application. The body |
| 280 | of the taglib-uri element may be either an |
| 281 | absolute URI specification, or a relative URI. |
| 282 | There should be no entries in web.xml with the |
| 283 | same taglib-uri value. |
| 284 | |
| 285 | </xsd:documentation> |
| 286 | </xsd:annotation> |
| 287 | </xsd:element> |
| 288 | |
| 289 | <xsd:element name="taglib-location" |
| 290 | type="j2ee:pathType"> |
| 291 | <xsd:annotation> |
| 292 | <xsd:documentation> |
| 293 | |
| 294 | the taglib-location element contains the location |
| 295 | (as a resource relative to the root of the web |
| 296 | application) where to find the Tag Library |
| 297 | Description file for the tag library. |
| 298 | |
| 299 | </xsd:documentation> |
| 300 | </xsd:annotation> |
| 301 | </xsd:element> |
| 302 | |
| 303 | </xsd:sequence> |
| 304 | <xsd:attribute name="id" type="xsd:ID"/> |
| 305 | </xsd:complexType> |
| 306 | |
| 307 | </xsd:schema> |
| 308 | |