glassfish 0.1.1-universal-java-1.5

Sign up to get free protection for your applications and to get access to all the features.
Files changed (135) hide show
  1. data/COPYRIGHT +33 -0
  2. data/LICENSE.txt +263 -0
  3. data/README +12 -0
  4. data/bin/asadmin +7 -0
  5. data/bin/asadmin.bat +8 -0
  6. data/bin/glassfish_rails +40 -0
  7. data/config/asadminenv.conf +6 -0
  8. data/config/asenv.bat +28 -0
  9. data/config/asenv.conf +27 -0
  10. data/config/glassfish.container +4 -0
  11. data/domains/domain1/config/admin-keyfile +3 -0
  12. data/domains/domain1/config/cacerts.jks +0 -0
  13. data/domains/domain1/config/default-web.xml +906 -0
  14. data/domains/domain1/config/domain-passwords +0 -0
  15. data/domains/domain1/config/domain.xml +208 -0
  16. data/domains/domain1/config/keyfile +6 -0
  17. data/domains/domain1/config/keystore.jks +0 -0
  18. data/domains/domain1/config/logging.properties +82 -0
  19. data/domains/domain1/config/login.conf +18 -0
  20. data/domains/domain1/config/server.policy +160 -0
  21. data/domains/domain1/config/sun-acc.xml +40 -0
  22. data/domains/domain1/config/wss-server-config-1.0.xml +86 -0
  23. data/domains/domain1/config/wss-server-config-2.0.xml +94 -0
  24. data/domains/domain1/docroot/favicon.gif +0 -0
  25. data/domains/domain1/docroot/index.html +87 -0
  26. data/domains/domain1/master-password +0 -0
  27. data/lib/appclient/appclientlogin.conf +10 -0
  28. data/lib/appclient/client.policy +79 -0
  29. data/lib/appclient/wss-client-config-1.0.xml +84 -0
  30. data/lib/appclient/wss-client-config-2.0.xml +96 -0
  31. data/lib/dtds/application-client_1_2.dtd +292 -0
  32. data/lib/dtds/application-client_1_3.dtd +506 -0
  33. data/lib/dtds/application_1_2.dtd +197 -0
  34. data/lib/dtds/application_1_3.dtd +312 -0
  35. data/lib/dtds/connector_1_0.dtd +561 -0
  36. data/lib/dtds/ejb-jar_1_1.dtd +894 -0
  37. data/lib/dtds/ejb-jar_2_0.dtd +1671 -0
  38. data/lib/dtds/sun-application-client-container_1_0.dtd +123 -0
  39. data/lib/dtds/sun-application-client-container_1_1.dtd +264 -0
  40. data/lib/dtds/sun-application-client-container_1_2.dtd +267 -0
  41. data/lib/dtds/sun-application-client_1_3-0.dtd +57 -0
  42. data/lib/dtds/sun-application-client_1_4-0.dtd +182 -0
  43. data/lib/dtds/sun-application-client_1_4-1.dtd +431 -0
  44. data/lib/dtds/sun-application-client_5_0-0.dtd +495 -0
  45. data/lib/dtds/sun-application_1_3-0.dtd +30 -0
  46. data/lib/dtds/sun-application_1_4-0.dtd +44 -0
  47. data/lib/dtds/sun-application_5_0-0.dtd +51 -0
  48. data/lib/dtds/sun-cmp-mapping_1_0.dtd +100 -0
  49. data/lib/dtds/sun-cmp-mapping_1_1.dtd +99 -0
  50. data/lib/dtds/sun-cmp-mapping_1_2.dtd +106 -0
  51. data/lib/dtds/sun-connector_1_0-0.dtd +66 -0
  52. data/lib/dtds/sun-connector_1_5-0.dtd +62 -0
  53. data/lib/dtds/sun-domain_1_0.dtd +2007 -0
  54. data/lib/dtds/sun-domain_1_1.dtd +3080 -0
  55. data/lib/dtds/sun-domain_1_2.dtd +3697 -0
  56. data/lib/dtds/sun-domain_1_3.dtd +3867 -0
  57. data/lib/dtds/sun-ejb-jar_2_0-0.dtd +449 -0
  58. data/lib/dtds/sun-ejb-jar_2_0-1.dtd +454 -0
  59. data/lib/dtds/sun-ejb-jar_2_1-0.dtd +756 -0
  60. data/lib/dtds/sun-ejb-jar_2_1-1.dtd +1085 -0
  61. data/lib/dtds/sun-ejb-jar_3_0-0.dtd +1113 -0
  62. data/lib/dtds/sun-loadbalancer_1_0.dtd +156 -0
  63. data/lib/dtds/sun-loadbalancer_1_1.dtd +172 -0
  64. data/lib/dtds/sun-resources_1_0.dtd +650 -0
  65. data/lib/dtds/sun-resources_1_1.dtd +650 -0
  66. data/lib/dtds/sun-resources_1_2.dtd +662 -0
  67. data/lib/dtds/sun-resources_1_3.dtd +732 -0
  68. data/lib/dtds/sun-server_1_0.dtd +1056 -0
  69. data/lib/dtds/sun-web-app_2_3-0.dtd +230 -0
  70. data/lib/dtds/sun-web-app_2_3-1.dtd +230 -0
  71. data/lib/dtds/sun-web-app_2_4-0.dtd +466 -0
  72. data/lib/dtds/sun-web-app_2_4-1.dtd +742 -0
  73. data/lib/dtds/sun-web-app_2_5-0.dtd +789 -0
  74. data/lib/dtds/web-app_2_2.dtd +639 -0
  75. data/lib/dtds/web-app_2_3.dtd +1063 -0
  76. data/lib/dtds/web-jsptaglibrary_1_1.dtd +265 -0
  77. data/lib/dtds/web-jsptaglibrary_1_2.dtd +468 -0
  78. data/lib/package-appclient.xml +185 -0
  79. data/lib/processLauncher.properties +25 -0
  80. data/lib/processLauncher.xml +189 -0
  81. data/lib/schemas/XMLSchema.dtd +402 -0
  82. data/lib/schemas/application-client_1_4.xsd +267 -0
  83. data/lib/schemas/application-client_5.xsd +304 -0
  84. data/lib/schemas/application_1_4.xsd +315 -0
  85. data/lib/schemas/application_5.xsd +336 -0
  86. data/lib/schemas/connector_1_5.xsd +1036 -0
  87. data/lib/schemas/datatypes.dtd +203 -0
  88. data/lib/schemas/ejb-jar_2_1.xsd +2208 -0
  89. data/lib/schemas/ejb-jar_3_0.xsd +2706 -0
  90. data/lib/schemas/j2ee_1_4.xsd +1608 -0
  91. data/lib/schemas/j2ee_jaxrpc_mapping_1_1.xsd +886 -0
  92. data/lib/schemas/j2ee_web_services_1_1.xsd +491 -0
  93. data/lib/schemas/j2ee_web_services_client_1_1.xsd +345 -0
  94. data/lib/schemas/javaee_5.xsd +2096 -0
  95. data/lib/schemas/javaee_web_services_1_2.xsd +747 -0
  96. data/lib/schemas/javaee_web_services_client_1_2.xsd +578 -0
  97. data/lib/schemas/jax-rpc-ri-config.xsd +416 -0
  98. data/lib/schemas/jsp_2_0.xsd +308 -0
  99. data/lib/schemas/jsp_2_1.xsd +343 -0
  100. data/lib/schemas/orm_1_0.xsd +1516 -0
  101. data/lib/schemas/persistence_1_0.xsd +260 -0
  102. data/lib/schemas/web-app_2_4.xsd +1234 -0
  103. data/lib/schemas/web-app_2_5.xsd +1271 -0
  104. data/lib/schemas/web-jsptaglibrary_2_0.xsd +1010 -0
  105. data/lib/schemas/web-jsptaglibrary_2_1.xsd +1144 -0
  106. data/lib/schemas/xml.xsd +82 -0
  107. data/modules/admin-cli-10.0-SNAPSHOT.jar +0 -0
  108. data/modules/auto-depends-0.2-SNAPSHOT.jar +0 -0
  109. data/modules/cli-framework-10.0-SNAPSHOT.jar +0 -0
  110. data/modules/common-ee-util-10.0-SNAPSHOT.jar +0 -0
  111. data/modules/common-util-10.0-SNAPSHOT.jar +0 -0
  112. data/modules/config-0.2-SNAPSHOT.jar +0 -0
  113. data/modules/config-api-10.0-SNAPSHOT.jar +0 -0
  114. data/modules/gf-jruby-connector-10.0-SNAPSHOT.jar +0 -0
  115. data/modules/glassfish-10.0-SNAPSHOT.jar +0 -0
  116. data/modules/glassfish-api-10.0-SNAPSHOT.jar +0 -0
  117. data/modules/glassfish.rb +10 -0
  118. data/modules/grizzly-framework-1.7.1.jar +0 -0
  119. data/modules/grizzly-http-1.7.1.jar +0 -0
  120. data/modules/grizzly-http-utils-1.7.1.jar +0 -0
  121. data/modules/grizzly-jruby-1.7.0.jar +0 -0
  122. data/modules/grizzly-jruby-module-1.7.0.jar +0 -0
  123. data/modules/grizzly-module-1.7.1.jar +0 -0
  124. data/modules/grizzly-portunif-1.7.1.jar +0 -0
  125. data/modules/grizzly-rcm-1.7.1.jar +0 -0
  126. data/modules/hk2-0.2-SNAPSHOT.jar +0 -0
  127. data/modules/hk2-core-0.2-SNAPSHOT.jar +0 -0
  128. data/modules/junit-4.3.1.jar +0 -0
  129. data/modules/kernel-10.0-SNAPSHOT.jar +0 -0
  130. data/modules/persistence-api-1.0b.jar +0 -0
  131. data/modules/servlet-api-2.5.jar +0 -0
  132. data/modules/sjsxp-1.0.jar +0 -0
  133. data/modules/stax-api-1.0-2.jar +0 -0
  134. data/modules/tiger-types-1.0.jar +0 -0
  135. metadata +206 -0
@@ -0,0 +1,260 @@
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <!-- persistence.xml schema -->
3
+ <xsd:schema targetNamespace="http://java.sun.com/xml/ns/persistence"
4
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
5
+ xmlns:persistence="http://java.sun.com/xml/ns/persistence"
6
+ elementFormDefault="qualified"
7
+ attributeFormDefault="unqualified"
8
+ version="1.0">
9
+
10
+ <xsd:annotation>
11
+ <xsd:documentation>
12
+ @(#)persistence_1_0.xsd 1.0 Feb 9 2006
13
+ </xsd:documentation>
14
+ </xsd:annotation>
15
+ <xsd:annotation>
16
+ <xsd:documentation><![CDATA[
17
+
18
+ This is the XML Schema for the persistence configuration file.
19
+ The file must be named "META-INF/persistence.xml" in the
20
+ persistence archive.
21
+ Persistence configuration files must indicate
22
+ the persistence schema by using the persistence namespace:
23
+
24
+ http://java.sun.com/xml/ns/persistence
25
+
26
+ and indicate the version of the schema by
27
+ using the version element as shown below:
28
+
29
+ <persistence xmlns="http://java.sun.com/xml/ns/persistence"
30
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
31
+ xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
32
+ http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
33
+ version="1.0">
34
+ ...
35
+ </persistence>
36
+
37
+ ]]></xsd:documentation>
38
+ </xsd:annotation>
39
+
40
+ <xsd:simpleType name="versionType">
41
+ <xsd:restriction base="xsd:token">
42
+ <xsd:pattern value="[0-9]+(\.[0-9]+)*"/>
43
+ </xsd:restriction>
44
+ </xsd:simpleType>
45
+
46
+ <!-- **************************************************** -->
47
+
48
+ <xsd:element name="persistence">
49
+ <xsd:complexType>
50
+ <xsd:sequence>
51
+
52
+ <!-- **************************************************** -->
53
+
54
+ <xsd:element name="persistence-unit"
55
+ minOccurs="0" maxOccurs="unbounded">
56
+ <xsd:complexType>
57
+ <xsd:annotation>
58
+ <xsd:documentation>
59
+
60
+ Configuration of a persistence unit.
61
+
62
+ </xsd:documentation>
63
+ </xsd:annotation>
64
+ <xsd:sequence>
65
+
66
+ <!-- **************************************************** -->
67
+
68
+ <xsd:element name="description" type="xsd:string"
69
+ minOccurs="0">
70
+ <xsd:annotation>
71
+ <xsd:documentation>
72
+
73
+ Textual description of this persistence unit.
74
+
75
+ </xsd:documentation>
76
+ </xsd:annotation>
77
+ </xsd:element>
78
+
79
+ <!-- **************************************************** -->
80
+
81
+ <xsd:element name="provider" type="xsd:string"
82
+ minOccurs="0">
83
+ <xsd:annotation>
84
+ <xsd:documentation>
85
+
86
+ Provider class that supplies EntityManagers for this
87
+ persistence unit.
88
+
89
+ </xsd:documentation>
90
+ </xsd:annotation>
91
+ </xsd:element>
92
+
93
+ <!-- **************************************************** -->
94
+
95
+ <xsd:element name="jta-data-source" type="xsd:string"
96
+ minOccurs="0">
97
+ <xsd:annotation>
98
+ <xsd:documentation>
99
+
100
+ The container-specific name of the JTA datasource to use.
101
+
102
+ </xsd:documentation>
103
+ </xsd:annotation>
104
+ </xsd:element>
105
+
106
+ <!-- **************************************************** -->
107
+
108
+ <xsd:element name="non-jta-data-source" type="xsd:string"
109
+ minOccurs="0">
110
+ <xsd:annotation>
111
+ <xsd:documentation>
112
+
113
+ The container-specific name of a non-JTA datasource to use.
114
+
115
+ </xsd:documentation>
116
+ </xsd:annotation>
117
+ </xsd:element>
118
+
119
+ <!-- **************************************************** -->
120
+
121
+ <xsd:element name="mapping-file" type="xsd:string"
122
+ minOccurs="0" maxOccurs="unbounded">
123
+ <xsd:annotation>
124
+ <xsd:documentation>
125
+
126
+ File containing mapping information. Loaded as a resource
127
+ by the persistence provider.
128
+
129
+ </xsd:documentation>
130
+ </xsd:annotation>
131
+ </xsd:element>
132
+
133
+ <!-- **************************************************** -->
134
+
135
+ <xsd:element name="jar-file" type="xsd:string"
136
+ minOccurs="0" maxOccurs="unbounded">
137
+ <xsd:annotation>
138
+ <xsd:documentation>
139
+
140
+ Jar file that should be scanned for entities.
141
+ Not applicable to Java SE persistence units.
142
+
143
+ </xsd:documentation>
144
+ </xsd:annotation>
145
+ </xsd:element>
146
+
147
+ <!-- **************************************************** -->
148
+
149
+ <xsd:element name="class" type="xsd:string"
150
+ minOccurs="0" maxOccurs="unbounded">
151
+ <xsd:annotation>
152
+ <xsd:documentation>
153
+
154
+ Class to scan for annotations. It should be annotated
155
+ with either @Entity, @Embeddable or @MappedSuperclass.
156
+
157
+ </xsd:documentation>
158
+ </xsd:annotation>
159
+ </xsd:element>
160
+
161
+ <!-- **************************************************** -->
162
+
163
+ <xsd:element name="exclude-unlisted-classes" type="xsd:boolean"
164
+ default="false" minOccurs="0">
165
+ <xsd:annotation>
166
+ <xsd:documentation>
167
+
168
+ When set to true then only listed classes and jars will
169
+ be scanned for persistent classes, otherwise the enclosing
170
+ jar or directory will also be scanned. Not applicable to
171
+ Java SE persistence units.
172
+
173
+ </xsd:documentation>
174
+ </xsd:annotation>
175
+ </xsd:element>
176
+
177
+ <!-- **************************************************** -->
178
+
179
+ <xsd:element name="properties" minOccurs="0">
180
+ <xsd:annotation>
181
+ <xsd:documentation>
182
+
183
+ A list of vendor-specific properties.
184
+
185
+ </xsd:documentation>
186
+ </xsd:annotation>
187
+ <xsd:complexType>
188
+ <xsd:sequence>
189
+ <xsd:element name="property"
190
+ minOccurs="0" maxOccurs="unbounded">
191
+ <xsd:annotation>
192
+ <xsd:documentation>
193
+ A name-value pair.
194
+ </xsd:documentation>
195
+ </xsd:annotation>
196
+ <xsd:complexType>
197
+ <xsd:attribute name="name" type="xsd:string"
198
+ use="required"/>
199
+ <xsd:attribute name="value" type="xsd:string"
200
+ use="required"/>
201
+ </xsd:complexType>
202
+ </xsd:element>
203
+ </xsd:sequence>
204
+ </xsd:complexType>
205
+ </xsd:element>
206
+
207
+ </xsd:sequence>
208
+
209
+ <!-- **************************************************** -->
210
+
211
+ <xsd:attribute name="name" type="xsd:string" use="required">
212
+ <xsd:annotation>
213
+ <xsd:documentation>
214
+
215
+ Name used in code to reference this persistence unit.
216
+
217
+ </xsd:documentation>
218
+ </xsd:annotation>
219
+ </xsd:attribute>
220
+
221
+ <!-- **************************************************** -->
222
+
223
+ <xsd:attribute name="transaction-type"
224
+ type="persistence:persistence-unit-transaction-type">
225
+ <xsd:annotation>
226
+ <xsd:documentation>
227
+
228
+ Type of transactions used by EntityManagers from this
229
+ persistence unit.
230
+
231
+ </xsd:documentation>
232
+ </xsd:annotation>
233
+ </xsd:attribute>
234
+
235
+ </xsd:complexType>
236
+ </xsd:element>
237
+ </xsd:sequence>
238
+ <xsd:attribute name="version" type="persistence:versionType"
239
+ fixed="1.0" use="required"/>
240
+ </xsd:complexType>
241
+ </xsd:element>
242
+
243
+ <!-- **************************************************** -->
244
+
245
+ <xsd:simpleType name="persistence-unit-transaction-type">
246
+ <xsd:annotation>
247
+ <xsd:documentation>
248
+
249
+ public enum TransactionType { JTA, RESOURCE_LOCAL };
250
+
251
+ </xsd:documentation>
252
+ </xsd:annotation>
253
+ <xsd:restriction base="xsd:token">
254
+ <xsd:enumeration value="JTA"/>
255
+ <xsd:enumeration value="RESOURCE_LOCAL"/>
256
+ </xsd:restriction>
257
+ </xsd:simpleType>
258
+
259
+ </xsd:schema>
260
+
@@ -0,0 +1,1234 @@
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.4">
10
+ <xsd:annotation>
11
+ <xsd:documentation>
12
+ @(#)web-app_2_4.xsds 1.60 03/08/26
13
+ </xsd:documentation>
14
+ </xsd:annotation>
15
+
16
+ <xsd:annotation>
17
+ <xsd:documentation>
18
+
19
+ Copyright 2004 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
+ <![CDATA[
54
+
55
+ This is the XML Schema for the Servlet 2.4 deployment descriptor.
56
+ The deployment descriptor must be named "WEB-INF/web.xml" in the
57
+ web application's war file. All Servlet deployment descriptors
58
+ must indicate the web application schema by using the J2EE
59
+ namespace:
60
+
61
+ http://java.sun.com/xml/ns/j2ee
62
+
63
+ and by indicating the version of the schema by
64
+ using the version element as shown below:
65
+
66
+ <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
67
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
68
+ xsi:schemaLocation="..."
69
+ version="2.4">
70
+ ...
71
+ </web-app>
72
+
73
+ The instance documents may indicate the published version of
74
+ the schema using the xsi:schemaLocation attribute for J2EE
75
+ namespace with the following location:
76
+
77
+ http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd
78
+
79
+ ]]>
80
+ </xsd:documentation>
81
+ </xsd:annotation>
82
+
83
+ <xsd:annotation>
84
+ <xsd:documentation>
85
+
86
+ The following conventions apply to all J2EE
87
+ deployment descriptor elements unless indicated otherwise.
88
+
89
+ - In elements that specify a pathname to a file within the
90
+ same JAR file, relative filenames (i.e., those not
91
+ starting with "/") are considered relative to the root of
92
+ the JAR file's namespace. Absolute filenames (i.e., those
93
+ starting with "/") also specify names in the root of the
94
+ JAR file's namespace. In general, relative names are
95
+ preferred. The exception is .war files where absolute
96
+ names are preferred for consistency with the Servlet API.
97
+
98
+ </xsd:documentation>
99
+ </xsd:annotation>
100
+
101
+ <xsd:include schemaLocation="j2ee_1_4.xsd"/>
102
+ <xsd:include schemaLocation="jsp_2_0.xsd"/>
103
+
104
+
105
+ <!-- **************************************************** -->
106
+
107
+
108
+ <xsd:element name="web-app" type="j2ee:web-appType">
109
+ <xsd:annotation>
110
+ <xsd:documentation>
111
+
112
+ The web-app element is the root of the deployment
113
+ descriptor for a web application. Note that the sub-elements
114
+ of this element can be in the arbitrary order. Because of
115
+ that, the multiplicity of the elements of distributable,
116
+ session-config, welcome-file-list, jsp-config, login-config,
117
+ and locale-encoding-mapping-list was changed from "?" to "*"
118
+ in this schema. However, the deployment descriptor instance
119
+ file must not contain multiple elements of session-config,
120
+ jsp-config, and login-config. When there are multiple elements of
121
+ welcome-file-list or locale-encoding-mapping-list, the container
122
+ must concatinate the element contents. The multiple occurance
123
+ of the element distributable is redundant and the container
124
+ treats that case exactly in the same way when there is only
125
+ one distributable.
126
+
127
+ </xsd:documentation>
128
+ </xsd:annotation>
129
+
130
+ <xsd:unique name="web-app-servlet-name-uniqueness">
131
+ <xsd:annotation>
132
+ <xsd:documentation>
133
+
134
+ The servlet element contains the name of a servlet.
135
+ The name must be unique within the web application.
136
+
137
+ </xsd:documentation>
138
+ </xsd:annotation>
139
+ <xsd:selector xpath="j2ee:servlet"/>
140
+ <xsd:field xpath="j2ee:servlet-name"/>
141
+ </xsd:unique>
142
+
143
+ <xsd:unique name="web-app-filter-name-uniqueness">
144
+ <xsd:annotation>
145
+ <xsd:documentation>
146
+
147
+ The filter element contains the name of a filter.
148
+ The name must be unique within the web application.
149
+
150
+ </xsd:documentation>
151
+ </xsd:annotation>
152
+ <xsd:selector xpath="j2ee:filter"/>
153
+ <xsd:field xpath="j2ee:filter-name"/>
154
+ </xsd:unique>
155
+
156
+ <xsd:unique name="web-app-ejb-local-ref-name-uniqueness">
157
+ <xsd:annotation>
158
+ <xsd:documentation>
159
+
160
+ The ejb-local-ref-name element contains the name of an EJB
161
+ reference. The EJB reference is an entry in the web
162
+ application's environment and is relative to the
163
+ java:comp/env context. The name must be unique within
164
+ the web application.
165
+
166
+ It is recommended that name is prefixed with "ejb/".
167
+
168
+ </xsd:documentation>
169
+ </xsd:annotation>
170
+ <xsd:selector xpath="j2ee:ejb-local-ref"/>
171
+ <xsd:field xpath="j2ee:ejb-ref-name"/>
172
+ </xsd:unique>
173
+
174
+ <xsd:unique name="web-app-ejb-ref-name-uniqueness">
175
+ <xsd:annotation>
176
+ <xsd:documentation>
177
+
178
+ The ejb-ref-name element contains the name of an EJB
179
+ reference. The EJB reference is an entry in the web
180
+ application's environment and is relative to the
181
+ java:comp/env context. The name must be unique within
182
+ the web application.
183
+
184
+ It is recommended that name is prefixed with "ejb/".
185
+
186
+ </xsd:documentation>
187
+ </xsd:annotation>
188
+ <xsd:selector xpath="j2ee:ejb-ref"/>
189
+ <xsd:field xpath="j2ee:ejb-ref-name"/>
190
+ </xsd:unique>
191
+
192
+ <xsd:unique name="web-app-resource-env-ref-uniqueness">
193
+ <xsd:annotation>
194
+ <xsd:documentation>
195
+
196
+ The resource-env-ref-name element specifies the name of
197
+ a resource environment reference; its value is the
198
+ environment entry name used in the web application code.
199
+ The name is a JNDI name relative to the java:comp/env
200
+ context and must be unique within a web application.
201
+
202
+ </xsd:documentation>
203
+ </xsd:annotation>
204
+ <xsd:selector xpath="j2ee:resource-env-ref"/>
205
+ <xsd:field xpath="j2ee:resource-env-ref-name"/>
206
+ </xsd:unique>
207
+
208
+ <xsd:unique name="web-app-message-destination-ref-uniqueness">
209
+ <xsd:annotation>
210
+ <xsd:documentation>
211
+
212
+ The message-destination-ref-name element specifies the name of
213
+ a message destination reference; its value is the
214
+ environment entry name used in the web application code.
215
+ The name is a JNDI name relative to the java:comp/env
216
+ context and must be unique within a web application.
217
+
218
+ </xsd:documentation>
219
+ </xsd:annotation>
220
+ <xsd:selector xpath="j2ee:message-destination-ref"/>
221
+ <xsd:field xpath="j2ee:message-destination-ref-name"/>
222
+ </xsd:unique>
223
+
224
+ <xsd:unique name="web-app-res-ref-name-uniqueness">
225
+ <xsd:annotation>
226
+ <xsd:documentation>
227
+
228
+ The res-ref-name element specifies the name of a
229
+ resource manager connection factory reference. The name
230
+ is a JNDI name relative to the java:comp/env context.
231
+ The name must be unique within a web application.
232
+
233
+ </xsd:documentation>
234
+ </xsd:annotation>
235
+ <xsd:selector xpath="j2ee:resource-ref"/>
236
+ <xsd:field xpath="j2ee:res-ref-name"/>
237
+ </xsd:unique>
238
+
239
+ <xsd:unique name="web-app-env-entry-name-uniqueness">
240
+ <xsd:annotation>
241
+ <xsd:documentation>
242
+
243
+ The env-entry-name element contains the name of a web
244
+ application's environment entry. The name is a JNDI
245
+ name relative to the java:comp/env context. The name
246
+ must be unique within a web application.
247
+
248
+ </xsd:documentation>
249
+ </xsd:annotation>
250
+
251
+ <xsd:selector xpath="j2ee:env-entry"/>
252
+ <xsd:field xpath="j2ee:env-entry-name"/>
253
+ </xsd:unique>
254
+
255
+ <xsd:key name="web-app-role-name-key">
256
+ <xsd:annotation>
257
+ <xsd:documentation>
258
+
259
+ A role-name-key is specified to allow the references
260
+ from the security-role-refs.
261
+
262
+ </xsd:documentation>
263
+ </xsd:annotation>
264
+ <xsd:selector xpath="j2ee:security-role"/>
265
+ <xsd:field xpath="j2ee:role-name"/>
266
+ </xsd:key>
267
+
268
+ <xsd:keyref name="web-app-role-name-references"
269
+ refer="j2ee:web-app-role-name-key">
270
+ <xsd:annotation>
271
+ <xsd:documentation>
272
+
273
+ The keyref indicates the references from
274
+ security-role-ref to a specified role-name.
275
+
276
+ </xsd:documentation>
277
+ </xsd:annotation>
278
+ <xsd:selector xpath="j2ee:servlet/j2ee:security-role-ref"/>
279
+ <xsd:field xpath="j2ee:role-link"/>
280
+ </xsd:keyref>
281
+ </xsd:element>
282
+
283
+
284
+ <!-- **************************************************** -->
285
+
286
+ <xsd:complexType name="auth-constraintType">
287
+ <xsd:annotation>
288
+ <xsd:documentation>
289
+
290
+ The auth-constraintType indicates the user roles that
291
+ should be permitted access to this resource
292
+ collection. The role-name used here must either correspond
293
+ to the role-name of one of the security-role elements
294
+ defined for this web application, or be the specially
295
+ reserved role-name "*" that is a compact syntax for
296
+ indicating all roles in the web application. If both "*"
297
+ and rolenames appear, the container interprets this as all
298
+ roles. If no roles are defined, no user is allowed access
299
+ to the portion of the web application described by the
300
+ containing security-constraint. The container matches
301
+ role names case sensitively when determining access.
302
+
303
+ </xsd:documentation>
304
+ </xsd:annotation>
305
+
306
+ <xsd:sequence>
307
+ <xsd:element name="description"
308
+ type="j2ee:descriptionType"
309
+ minOccurs="0" maxOccurs="unbounded"/>
310
+ <xsd:element name="role-name"
311
+ type="j2ee:role-nameType"
312
+ minOccurs="0" maxOccurs="unbounded"/>
313
+ </xsd:sequence>
314
+ <xsd:attribute name="id" type="xsd:ID"/>
315
+ </xsd:complexType>
316
+
317
+ <!-- **************************************************** -->
318
+
319
+ <xsd:complexType name="auth-methodType">
320
+ <xsd:annotation>
321
+ <xsd:documentation>
322
+
323
+ The auth-methodType is used to configure the authentication
324
+ mechanism for the web application. As a prerequisite to
325
+ gaining access to any web resources which are protected by
326
+ an authorization constraint, a user must have authenticated
327
+ using the configured mechanism. Legal values are "BASIC",
328
+ "DIGEST", "FORM", "CLIENT-CERT", or a vendor-specific
329
+ authentication scheme.
330
+
331
+ Used in: login-config
332
+
333
+ </xsd:documentation>
334
+ </xsd:annotation>
335
+
336
+ <xsd:simpleContent>
337
+ <xsd:restriction base="j2ee:string"/>
338
+ </xsd:simpleContent>
339
+ </xsd:complexType>
340
+
341
+ <!-- **************************************************** -->
342
+
343
+ <xsd:complexType name="dispatcherType">
344
+ <xsd:annotation>
345
+ <xsd:documentation>
346
+
347
+ The dispatcher has four legal values: FORWARD, REQUEST, INCLUDE,
348
+ and ERROR. A value of FORWARD means the Filter will be applied
349
+ under RequestDispatcher.forward() calls. A value of REQUEST
350
+ means the Filter will be applied under ordinary client calls to
351
+ the path or servlet. A value of INCLUDE means the Filter will be
352
+ applied under RequestDispatcher.include() calls. A value of
353
+ ERROR means the Filter will be applied under the error page
354
+ mechanism. The absence of any dispatcher elements in a
355
+ filter-mapping indicates a default of applying filters only under
356
+ ordinary client calls to the path or servlet.
357
+
358
+ </xsd:documentation>
359
+ </xsd:annotation>
360
+
361
+ <xsd:simpleContent>
362
+ <xsd:restriction base="j2ee:string">
363
+ <xsd:enumeration value="FORWARD"/>
364
+ <xsd:enumeration value="INCLUDE"/>
365
+ <xsd:enumeration value="REQUEST"/>
366
+ <xsd:enumeration value="ERROR"/>
367
+ </xsd:restriction>
368
+ </xsd:simpleContent>
369
+ </xsd:complexType>
370
+
371
+ <!-- **************************************************** -->
372
+
373
+ <xsd:simpleType name="encodingType">
374
+ <xsd:annotation>
375
+ <xsd:documentation>
376
+
377
+ The encodingType defines IANA character sets.
378
+
379
+ </xsd:documentation>
380
+ </xsd:annotation>
381
+
382
+ <xsd:restriction base="xsd:string">
383
+ <xsd:pattern value="[^\s]+"/>
384
+ </xsd:restriction>
385
+ </xsd:simpleType>
386
+
387
+ <!-- **************************************************** -->
388
+
389
+ <xsd:complexType name="error-codeType">
390
+ <xsd:annotation>
391
+ <xsd:documentation>
392
+
393
+ The error-code contains an HTTP error code, ex: 404
394
+
395
+ Used in: error-page
396
+
397
+ </xsd:documentation>
398
+ </xsd:annotation>
399
+
400
+ <xsd:simpleContent>
401
+ <xsd:restriction base="j2ee:xsdPositiveIntegerType">
402
+ <xsd:pattern value="\d{3}"/>
403
+ <xsd:attribute name="id" type="xsd:ID"/>
404
+ </xsd:restriction>
405
+ </xsd:simpleContent>
406
+ </xsd:complexType>
407
+
408
+ <!-- **************************************************** -->
409
+
410
+ <xsd:complexType name="error-pageType">
411
+ <xsd:annotation>
412
+ <xsd:documentation>
413
+
414
+ The error-pageType contains a mapping between an error code
415
+ or exception type to the path of a resource in the web
416
+ application.
417
+
418
+ Used in: web-app
419
+
420
+ </xsd:documentation>
421
+ </xsd:annotation>
422
+
423
+ <xsd:sequence>
424
+ <xsd:choice>
425
+ <xsd:element name="error-code"
426
+ type="j2ee:error-codeType"/>
427
+
428
+ <xsd:element name="exception-type"
429
+ type="j2ee:fully-qualified-classType">
430
+ <xsd:annotation>
431
+ <xsd:documentation>
432
+
433
+ The exception-type contains a fully qualified class
434
+ name of a Java exception type.
435
+
436
+ </xsd:documentation>
437
+ </xsd:annotation>
438
+ </xsd:element>
439
+ </xsd:choice>
440
+
441
+ <xsd:element name="location"
442
+ type="j2ee:war-pathType">
443
+ <xsd:annotation>
444
+ <xsd:documentation>
445
+
446
+ The location element contains the location of the
447
+ resource in the web application relative to the root of
448
+ the web application. The value of the location must have
449
+ a leading `/'.
450
+
451
+ </xsd:documentation>
452
+ </xsd:annotation>
453
+ </xsd:element>
454
+ </xsd:sequence>
455
+ <xsd:attribute name="id" type="xsd:ID"/>
456
+ </xsd:complexType>
457
+
458
+ <!-- **************************************************** -->
459
+
460
+ <xsd:complexType name="filter-mappingType">
461
+ <xsd:annotation>
462
+ <xsd:documentation>
463
+
464
+ Declaration of the filter mappings in this web
465
+ application is done by using filter-mappingType.
466
+ The container uses the filter-mapping
467
+ declarations to decide which filters to apply to a request,
468
+ and in what order. The container matches the request URI to
469
+ a Servlet in the normal way. To determine which filters to
470
+ apply it matches filter-mapping declarations either on
471
+ servlet-name, or on url-pattern for each filter-mapping
472
+ element, depending on which style is used. The order in
473
+ which filters are invoked is the order in which
474
+ filter-mapping declarations that match a request URI for a
475
+ servlet appear in the list of filter-mapping elements.The
476
+ filter-name value must be the value of the filter-name
477
+ sub-elements of one of the filter declarations in the
478
+ deployment descriptor.
479
+
480
+ </xsd:documentation>
481
+ </xsd:annotation>
482
+
483
+ <xsd:sequence>
484
+ <xsd:element name="filter-name"
485
+ type="j2ee:filter-nameType"/>
486
+ <xsd:choice>
487
+ <xsd:element name="url-pattern"
488
+ type="j2ee:url-patternType"/>
489
+ <xsd:element name="servlet-name"
490
+ type="j2ee:servlet-nameType"/>
491
+ </xsd:choice>
492
+ <xsd:element name="dispatcher"
493
+ type="j2ee:dispatcherType"
494
+ minOccurs="0" maxOccurs="4"/>
495
+ </xsd:sequence>
496
+ <xsd:attribute name="id" type="xsd:ID"/>
497
+ </xsd:complexType>
498
+
499
+ <!-- **************************************************** -->
500
+
501
+ <xsd:complexType name="filter-nameType">
502
+ <xsd:annotation>
503
+ <xsd:documentation>
504
+
505
+ The logical name of the filter is declare
506
+ by using filter-nameType. This name is used to map the
507
+ filter. Each filter name is unique within the web
508
+ application.
509
+
510
+ Used in: filter, filter-mapping
511
+
512
+ </xsd:documentation>
513
+ </xsd:annotation>
514
+
515
+ <xsd:simpleContent>
516
+ <xsd:extension base="j2ee:nonEmptyStringType"/>
517
+ </xsd:simpleContent>
518
+ </xsd:complexType>
519
+
520
+ <!-- **************************************************** -->
521
+
522
+ <xsd:complexType name="filterType">
523
+ <xsd:annotation>
524
+ <xsd:documentation>
525
+
526
+ The filterType is used to declare a filter in the web
527
+ application. The filter is mapped to either a servlet or a
528
+ URL pattern in the filter-mapping element, using the
529
+ filter-name value to reference. Filters can access the
530
+ initialization parameters declared in the deployment
531
+ descriptor at runtime via the FilterConfig interface.
532
+
533
+ Used in: web-app
534
+
535
+ </xsd:documentation>
536
+ </xsd:annotation>
537
+
538
+ <xsd:sequence>
539
+ <xsd:group ref="j2ee:descriptionGroup"/>
540
+ <xsd:element name="filter-name"
541
+ type="j2ee:filter-nameType"/>
542
+ <xsd:element name="filter-class"
543
+ type="j2ee:fully-qualified-classType">
544
+ <xsd:annotation>
545
+ <xsd:documentation>
546
+
547
+ The fully qualified classname of the filter.
548
+
549
+ </xsd:documentation>
550
+ </xsd:annotation>
551
+ </xsd:element>
552
+
553
+ <xsd:element name="init-param"
554
+ type="j2ee:param-valueType"
555
+ minOccurs="0" maxOccurs="unbounded">
556
+ <xsd:annotation>
557
+ <xsd:documentation>
558
+
559
+ The init-param element contains a name/value pair as
560
+ an initialization param of a servlet filter
561
+
562
+ </xsd:documentation>
563
+ </xsd:annotation>
564
+ </xsd:element>
565
+ </xsd:sequence>
566
+ <xsd:attribute name="id" type="xsd:ID"/>
567
+ </xsd:complexType>
568
+
569
+ <!-- **************************************************** -->
570
+
571
+ <xsd:complexType name="form-login-configType">
572
+ <xsd:annotation>
573
+ <xsd:documentation>
574
+
575
+ The form-login-configType specifies the login and error
576
+ pages that should be used in form based login. If form based
577
+ authentication is not used, these elements are ignored.
578
+
579
+ Used in: login-config
580
+
581
+ </xsd:documentation>
582
+ </xsd:annotation>
583
+
584
+ <xsd:sequence>
585
+
586
+ <xsd:element name="form-login-page"
587
+ type="j2ee:war-pathType">
588
+ <xsd:annotation>
589
+ <xsd:documentation>
590
+
591
+ The form-login-page element defines the location in the web
592
+ app where the page that can be used for login can be
593
+ found. The path begins with a leading / and is interpreted
594
+ relative to the root of the WAR.
595
+
596
+ </xsd:documentation>
597
+ </xsd:annotation>
598
+ </xsd:element>
599
+
600
+ <xsd:element name="form-error-page"
601
+ type="j2ee:war-pathType">
602
+ <xsd:annotation>
603
+ <xsd:documentation>
604
+
605
+ The form-error-page element defines the location in
606
+ the web app where the error page that is displayed
607
+ when login is not successful can be found.
608
+ The path begins with a leading / and is interpreted
609
+ relative to the root of the WAR.
610
+
611
+ </xsd:documentation>
612
+ </xsd:annotation>
613
+ </xsd:element>
614
+
615
+ </xsd:sequence>
616
+ <xsd:attribute name="id" type="xsd:ID"/>
617
+ </xsd:complexType>
618
+
619
+ <!-- **************************************************** -->
620
+
621
+ <xsd:complexType name="http-methodType">
622
+ <xsd:annotation>
623
+
624
+ <xsd:documentation>
625
+
626
+ The http-method contains an HTTP method recognized by the
627
+ web-app, for example GET, POST, ...
628
+
629
+ </xsd:documentation>
630
+ </xsd:annotation>
631
+
632
+ <xsd:simpleContent>
633
+ <xsd:restriction base="j2ee:string">
634
+ <xsd:enumeration value="GET"/>
635
+ <xsd:enumeration value="POST"/>
636
+ <xsd:enumeration value="PUT"/>
637
+ <xsd:enumeration value="DELETE"/>
638
+ <xsd:enumeration value="HEAD"/>
639
+ <xsd:enumeration value="OPTIONS"/>
640
+ <xsd:enumeration value="TRACE"/>
641
+ </xsd:restriction>
642
+ </xsd:simpleContent>
643
+ </xsd:complexType>
644
+
645
+ <!-- **************************************************** -->
646
+
647
+ <xsd:complexType name="locale-encoding-mapping-listType">
648
+ <xsd:annotation>
649
+ <xsd:documentation>
650
+
651
+ The locale-encoding-mapping-list contains one or more
652
+ locale-encoding-mapping(s).
653
+
654
+ </xsd:documentation>
655
+ </xsd:annotation>
656
+
657
+ <xsd:sequence>
658
+ <xsd:element name="locale-encoding-mapping"
659
+ type="j2ee:locale-encoding-mappingType"
660
+ maxOccurs="unbounded"/>
661
+ </xsd:sequence>
662
+ <xsd:attribute name="id" type="xsd:ID"/>
663
+ </xsd:complexType>
664
+
665
+ <!-- **************************************************** -->
666
+
667
+ <xsd:complexType name="locale-encoding-mappingType">
668
+ <xsd:annotation>
669
+ <xsd:documentation>
670
+
671
+ The locale-encoding-mapping contains locale name and
672
+ encoding name. The locale name must be either "Language-code",
673
+ such as "ja", defined by ISO-639 or "Language-code_Country-code",
674
+ such as "ja_JP". "Country code" is defined by ISO-3166.
675
+
676
+ </xsd:documentation>
677
+ </xsd:annotation>
678
+
679
+ <xsd:sequence>
680
+ <xsd:element name="locale"
681
+ type="j2ee:localeType"/>
682
+ <xsd:element name="encoding"
683
+ type="j2ee:encodingType"/>
684
+ </xsd:sequence>
685
+ <xsd:attribute name="id" type="xsd:ID"/>
686
+ </xsd:complexType>
687
+
688
+ <!-- **************************************************** -->
689
+
690
+ <xsd:simpleType name="localeType">
691
+ <xsd:annotation>
692
+ <xsd:documentation>
693
+
694
+ The localeType defines valid locale defined by ISO-639-1
695
+ and ISO-3166.
696
+
697
+ </xsd:documentation>
698
+ </xsd:annotation>
699
+
700
+ <xsd:restriction base="xsd:string">
701
+ <xsd:pattern value="[a-z]{2}(_|-)?([\p{L}\-\p{Nd}]{2})?"/>
702
+ </xsd:restriction>
703
+ </xsd:simpleType>
704
+
705
+ <!-- **************************************************** -->
706
+
707
+ <xsd:complexType name="login-configType">
708
+ <xsd:annotation>
709
+ <xsd:documentation>
710
+
711
+ The login-configType is used to configure the authentication
712
+ method that should be used, the realm name that should be
713
+ used for this application, and the attributes that are
714
+ needed by the form login mechanism.
715
+
716
+ Used in: web-app
717
+
718
+ </xsd:documentation>
719
+ </xsd:annotation>
720
+
721
+ <xsd:sequence>
722
+ <xsd:element name="auth-method"
723
+ type="j2ee:auth-methodType"
724
+ minOccurs="0"/>
725
+ <xsd:element name="realm-name"
726
+ type="j2ee:string" minOccurs="0">
727
+ <xsd:annotation>
728
+ <xsd:documentation>
729
+
730
+ The realm name element specifies the realm name to
731
+ use in HTTP Basic authorization.
732
+
733
+ </xsd:documentation>
734
+ </xsd:annotation>
735
+ </xsd:element>
736
+ <xsd:element name="form-login-config"
737
+ type="j2ee:form-login-configType"
738
+ minOccurs="0"/>
739
+ </xsd:sequence>
740
+ <xsd:attribute name="id" type="xsd:ID"/>
741
+ </xsd:complexType>
742
+
743
+ <!-- **************************************************** -->
744
+
745
+ <xsd:complexType name="mime-mappingType">
746
+ <xsd:annotation>
747
+ <xsd:documentation>
748
+
749
+ The mime-mappingType defines a mapping between an extension
750
+ and a mime type.
751
+
752
+ Used in: web-app
753
+
754
+ </xsd:documentation>
755
+ </xsd:annotation>
756
+
757
+ <xsd:sequence>
758
+ <xsd:annotation>
759
+ <xsd:documentation>
760
+
761
+ The extension element contains a string describing an
762
+ extension. example: "txt"
763
+
764
+ </xsd:documentation>
765
+ </xsd:annotation>
766
+
767
+ <xsd:element name="extension"
768
+ type="j2ee:string"/>
769
+ <xsd:element name="mime-type"
770
+ type="j2ee:mime-typeType"/>
771
+ </xsd:sequence>
772
+ <xsd:attribute name="id" type="xsd:ID"/>
773
+ </xsd:complexType>
774
+
775
+ <!-- **************************************************** -->
776
+
777
+ <xsd:complexType name="mime-typeType">
778
+ <xsd:annotation>
779
+ <xsd:documentation>
780
+
781
+ The mime-typeType is used to indicate a defined mime type.
782
+
783
+ Example:
784
+ "text/plain"
785
+
786
+ Used in: mime-mapping
787
+
788
+ </xsd:documentation>
789
+ </xsd:annotation>
790
+
791
+ <xsd:simpleContent>
792
+ <xsd:restriction base="j2ee:string">
793
+ <xsd:pattern value="[^\p{Cc}^\s]+/[^\p{Cc}^\s]+"/>
794
+ </xsd:restriction>
795
+ </xsd:simpleContent>
796
+ </xsd:complexType>
797
+
798
+ <!-- **************************************************** -->
799
+
800
+ <xsd:complexType name="nonEmptyStringType">
801
+ <xsd:annotation>
802
+ <xsd:documentation>
803
+ This type defines a string which contains at least one
804
+ character.
805
+ </xsd:documentation>
806
+ </xsd:annotation>
807
+ <xsd:simpleContent>
808
+ <xsd:restriction base="j2ee:string">
809
+ <xsd:minLength value="1"/>
810
+ </xsd:restriction>
811
+ </xsd:simpleContent>
812
+ </xsd:complexType>
813
+
814
+ <!-- **************************************************** -->
815
+
816
+ <xsd:complexType name="security-constraintType">
817
+ <xsd:annotation>
818
+ <xsd:documentation>
819
+
820
+ The security-constraintType is used to associate
821
+ security constraints with one or more web resource
822
+ collections
823
+
824
+ Used in: web-app
825
+
826
+ </xsd:documentation>
827
+ </xsd:annotation>
828
+
829
+ <xsd:sequence>
830
+ <xsd:element name="display-name"
831
+ type="j2ee:display-nameType"
832
+ minOccurs="0"
833
+ maxOccurs="unbounded"/>
834
+ <xsd:element name="web-resource-collection"
835
+ type="j2ee:web-resource-collectionType"
836
+ maxOccurs="unbounded"/>
837
+ <xsd:element name="auth-constraint"
838
+ type="j2ee:auth-constraintType"
839
+ minOccurs="0"/>
840
+ <xsd:element name="user-data-constraint"
841
+ type="j2ee:user-data-constraintType"
842
+ minOccurs="0"/>
843
+ </xsd:sequence>
844
+ <xsd:attribute name="id" type="xsd:ID"/>
845
+ </xsd:complexType>
846
+
847
+ <!-- **************************************************** -->
848
+
849
+ <xsd:complexType name="servlet-mappingType">
850
+ <xsd:annotation>
851
+ <xsd:documentation>
852
+
853
+ The servlet-mappingType defines a mapping between a
854
+ servlet and a url pattern.
855
+
856
+ Used in: web-app
857
+
858
+ </xsd:documentation>
859
+ </xsd:annotation>
860
+
861
+ <xsd:sequence>
862
+ <xsd:element name="servlet-name"
863
+ type="j2ee:servlet-nameType"/>
864
+ <xsd:element name="url-pattern"
865
+ type="j2ee:url-patternType"/>
866
+ </xsd:sequence>
867
+ <xsd:attribute name="id" type="xsd:ID"/>
868
+ </xsd:complexType>
869
+
870
+ <!-- **************************************************** -->
871
+
872
+ <xsd:complexType name="servlet-nameType">
873
+ <xsd:annotation>
874
+ <xsd:documentation>
875
+
876
+ The servlet-name element contains the canonical name of the
877
+ servlet. Each servlet name is unique within the web
878
+ application.
879
+
880
+ </xsd:documentation>
881
+ </xsd:annotation>
882
+
883
+ <xsd:simpleContent>
884
+ <xsd:extension base="j2ee:nonEmptyStringType"/>
885
+ </xsd:simpleContent>
886
+ </xsd:complexType>
887
+
888
+ <!-- **************************************************** -->
889
+
890
+ <xsd:complexType name="servletType">
891
+ <xsd:annotation>
892
+ <xsd:documentation>
893
+
894
+ The servletType is used to declare a servlet.
895
+ It contains the declarative data of a
896
+ servlet. If a jsp-file is specified and the load-on-startup
897
+ element is present, then the JSP should be precompiled and
898
+ loaded.
899
+
900
+ Used in: web-app
901
+
902
+ </xsd:documentation>
903
+ </xsd:annotation>
904
+
905
+ <xsd:sequence>
906
+ <xsd:group ref="j2ee:descriptionGroup"/>
907
+ <xsd:element name="servlet-name"
908
+ type="j2ee:servlet-nameType"/>
909
+ <xsd:choice>
910
+ <xsd:element name="servlet-class"
911
+ type="j2ee:fully-qualified-classType">
912
+ <xsd:annotation>
913
+ <xsd:documentation>
914
+
915
+ The servlet-class element contains the fully
916
+ qualified class name of the servlet.
917
+
918
+ </xsd:documentation>
919
+ </xsd:annotation>
920
+ </xsd:element>
921
+
922
+ <xsd:element name="jsp-file"
923
+ type="j2ee:jsp-fileType"/>
924
+
925
+ </xsd:choice>
926
+
927
+ <xsd:element name="init-param"
928
+ type="j2ee:param-valueType"
929
+ minOccurs="0" maxOccurs="unbounded"/>
930
+ <xsd:element name="load-on-startup"
931
+ type="j2ee:xsdIntegerType"
932
+ minOccurs="0">
933
+ <xsd:annotation>
934
+ <xsd:documentation>
935
+
936
+ The load-on-startup element indicates that this
937
+ servlet should be loaded (instantiated and have
938
+ its init() called) on the startup of the web
939
+ application. The optional contents of these
940
+ element must be an integer indicating the order in
941
+ which the servlet should be loaded. If the value
942
+ is a negative integer, or the element is not
943
+ present, the container is free to load the servlet
944
+ whenever it chooses. If the value is a positive
945
+ integer or 0, the container must load and
946
+ initialize the servlet as the application is
947
+ deployed. The container must guarantee that
948
+ servlets marked with lower integers are loaded
949
+ before servlets marked with higher integers. The
950
+ container may choose the order of loading of
951
+ servlets with the same load-on-start-up value.
952
+
953
+ </xsd:documentation>
954
+ </xsd:annotation>
955
+ </xsd:element>
956
+ <xsd:element name="run-as"
957
+ type="j2ee:run-asType"
958
+ minOccurs="0"/>
959
+ <xsd:element name="security-role-ref"
960
+ type="j2ee:security-role-refType"
961
+ minOccurs="0" maxOccurs="unbounded"/>
962
+ </xsd:sequence>
963
+ <xsd:attribute name="id" type="xsd:ID"/>
964
+ </xsd:complexType>
965
+
966
+ <!-- **************************************************** -->
967
+
968
+ <xsd:complexType name="session-configType">
969
+ <xsd:annotation>
970
+ <xsd:documentation>
971
+
972
+ The session-configType defines the session parameters
973
+ for this web application.
974
+
975
+ Used in: web-app
976
+
977
+ </xsd:documentation>
978
+ </xsd:annotation>
979
+
980
+ <xsd:sequence>
981
+ <xsd:element name="session-timeout"
982
+ type="j2ee:xsdIntegerType"
983
+ minOccurs="0">
984
+ <xsd:annotation>
985
+ <xsd:documentation>
986
+
987
+ The session-timeout element defines the default
988
+ session timeout interval for all sessions created
989
+ in this web application. The specified timeout
990
+ must be expressed in a whole number of minutes.
991
+ If the timeout is 0 or less, the container ensures
992
+ the default behaviour of sessions is never to time
993
+ out. If this element is not specified, the container
994
+ must set its default timeout period.
995
+
996
+ </xsd:documentation>
997
+ </xsd:annotation>
998
+ </xsd:element>
999
+ </xsd:sequence>
1000
+ <xsd:attribute name="id" type="xsd:ID"/>
1001
+ </xsd:complexType>
1002
+
1003
+ <!-- **************************************************** -->
1004
+
1005
+ <xsd:complexType name="transport-guaranteeType">
1006
+ <xsd:annotation>
1007
+ <xsd:documentation>
1008
+
1009
+ The transport-guaranteeType specifies that the communication
1010
+ between client and server should be NONE, INTEGRAL, or
1011
+ CONFIDENTIAL. NONE means that the application does not
1012
+ require any transport guarantees. A value of INTEGRAL means
1013
+ that the application requires that the data sent between the
1014
+ client and server be sent in such a way that it can't be
1015
+ changed in transit. CONFIDENTIAL means that the application
1016
+ requires that the data be transmitted in a fashion that
1017
+ prevents other entities from observing the contents of the
1018
+ transmission. In most cases, the presence of the INTEGRAL or
1019
+ CONFIDENTIAL flag will indicate that the use of SSL is
1020
+ required.
1021
+
1022
+ Used in: user-data-constraint
1023
+
1024
+ </xsd:documentation>
1025
+ </xsd:annotation>
1026
+
1027
+ <xsd:simpleContent>
1028
+ <xsd:restriction base="j2ee:string">
1029
+ <xsd:enumeration value="NONE"/>
1030
+ <xsd:enumeration value="INTEGRAL"/>
1031
+ <xsd:enumeration value="CONFIDENTIAL"/>
1032
+ </xsd:restriction>
1033
+ </xsd:simpleContent>
1034
+ </xsd:complexType>
1035
+
1036
+ <!-- **************************************************** -->
1037
+
1038
+ <xsd:complexType name="user-data-constraintType">
1039
+ <xsd:annotation>
1040
+ <xsd:documentation>
1041
+
1042
+ The user-data-constraintType is used to indicate how
1043
+ data communicated between the client and container should be
1044
+ protected.
1045
+
1046
+ Used in: security-constraint
1047
+
1048
+ </xsd:documentation>
1049
+ </xsd:annotation>
1050
+
1051
+ <xsd:sequence>
1052
+ <xsd:element name="description"
1053
+ type="j2ee:descriptionType"
1054
+ minOccurs="0"
1055
+ maxOccurs="unbounded"/>
1056
+ <xsd:element name="transport-guarantee"
1057
+ type="j2ee:transport-guaranteeType"/>
1058
+ </xsd:sequence>
1059
+ <xsd:attribute name="id" type="xsd:ID"/>
1060
+ </xsd:complexType>
1061
+
1062
+ <!-- **************************************************** -->
1063
+
1064
+ <xsd:complexType name="war-pathType">
1065
+ <xsd:annotation>
1066
+ <xsd:documentation>
1067
+
1068
+ The elements that use this type designate a path starting
1069
+ with a "/" and interpreted relative to the root of a WAR
1070
+ file.
1071
+
1072
+ </xsd:documentation>
1073
+ </xsd:annotation>
1074
+ <xsd:simpleContent>
1075
+ <xsd:restriction base="j2ee:string">
1076
+ <xsd:pattern value="/.*"/>
1077
+ </xsd:restriction>
1078
+ </xsd:simpleContent>
1079
+ </xsd:complexType>
1080
+
1081
+ <!-- **************************************************** -->
1082
+
1083
+ <xsd:simpleType name="web-app-versionType">
1084
+ <xsd:annotation>
1085
+ <xsd:documentation>
1086
+
1087
+ This type contains the recognized versions of
1088
+ web-application supported. It is used to designate the
1089
+ version of the web application.
1090
+
1091
+ </xsd:documentation>
1092
+ </xsd:annotation>
1093
+ <xsd:restriction base="xsd:token">
1094
+ <xsd:enumeration value="2.4"/>
1095
+ </xsd:restriction>
1096
+ </xsd:simpleType>
1097
+
1098
+ <!-- **************************************************** -->
1099
+
1100
+ <xsd:complexType name="web-appType">
1101
+
1102
+ <xsd:choice minOccurs="0" maxOccurs="unbounded">
1103
+ <xsd:group ref="j2ee:descriptionGroup"/>
1104
+ <xsd:element name="distributable"
1105
+ type="j2ee:emptyType"/>
1106
+ <xsd:element name="context-param"
1107
+ type="j2ee:param-valueType">
1108
+
1109
+ <xsd:annotation>
1110
+ <xsd:documentation>
1111
+
1112
+ The context-param element contains the declaration
1113
+ of a web application's servlet context
1114
+ initialization parameters.
1115
+
1116
+ </xsd:documentation>
1117
+ </xsd:annotation>
1118
+ </xsd:element>
1119
+
1120
+ <xsd:element name="filter"
1121
+ type="j2ee:filterType"/>
1122
+ <xsd:element name="filter-mapping"
1123
+ type="j2ee:filter-mappingType"/>
1124
+ <xsd:element name="listener"
1125
+ type="j2ee:listenerType"/>
1126
+ <xsd:element name="servlet"
1127
+ type="j2ee:servletType"/>
1128
+ <xsd:element name="servlet-mapping"
1129
+ type="j2ee:servlet-mappingType"/>
1130
+ <xsd:element name="session-config"
1131
+ type="j2ee:session-configType"/>
1132
+ <xsd:element name="mime-mapping"
1133
+ type="j2ee:mime-mappingType"/>
1134
+ <xsd:element name="welcome-file-list"
1135
+ type="j2ee:welcome-file-listType"/>
1136
+ <xsd:element name="error-page"
1137
+ type="j2ee:error-pageType"/>
1138
+ <xsd:element name="jsp-config"
1139
+ type="j2ee:jsp-configType"/>
1140
+ <xsd:element name="security-constraint"
1141
+ type="j2ee:security-constraintType"/>
1142
+ <xsd:element name="login-config"
1143
+ type="j2ee:login-configType"/>
1144
+ <xsd:element name="security-role"
1145
+ type="j2ee:security-roleType"/>
1146
+ <xsd:group ref="j2ee:jndiEnvironmentRefsGroup"/>
1147
+ <xsd:element name="message-destination"
1148
+ type="j2ee:message-destinationType"/>
1149
+ <xsd:element name="locale-encoding-mapping-list"
1150
+ type="j2ee:locale-encoding-mapping-listType"/>
1151
+ </xsd:choice>
1152
+
1153
+ <xsd:attribute name="version"
1154
+ type="j2ee:web-app-versionType"
1155
+ use="required"/>
1156
+ <xsd:attribute name="id" type="xsd:ID"/>
1157
+ </xsd:complexType>
1158
+
1159
+ <!-- **************************************************** -->
1160
+
1161
+ <xsd:complexType name="web-resource-collectionType">
1162
+ <xsd:annotation>
1163
+ <xsd:documentation>
1164
+
1165
+ The web-resource-collectionType is used to identify a subset
1166
+ of the resources and HTTP methods on those resources within
1167
+ a web application to which a security constraint applies. If
1168
+ no HTTP methods are specified, then the security constraint
1169
+ applies to all HTTP methods.
1170
+
1171
+ Used in: security-constraint
1172
+
1173
+ </xsd:documentation>
1174
+ </xsd:annotation>
1175
+
1176
+ <xsd:sequence>
1177
+ <xsd:element name="web-resource-name"
1178
+ type="j2ee:string">
1179
+ <xsd:annotation>
1180
+ <xsd:documentation>
1181
+
1182
+ The web-resource-name contains the name of this web
1183
+ resource collection.
1184
+
1185
+ </xsd:documentation>
1186
+ </xsd:annotation>
1187
+ </xsd:element>
1188
+ <xsd:element name="description"
1189
+ type="j2ee:descriptionType"
1190
+ minOccurs="0"
1191
+ maxOccurs="unbounded"/>
1192
+ <xsd:element name="url-pattern"
1193
+ type="j2ee:url-patternType"
1194
+ maxOccurs="unbounded"/>
1195
+ <xsd:element name="http-method"
1196
+ type="j2ee:http-methodType"
1197
+ minOccurs="0" maxOccurs="unbounded"/>
1198
+ </xsd:sequence>
1199
+ <xsd:attribute name="id" type="xsd:ID"/>
1200
+ </xsd:complexType>
1201
+
1202
+ <!-- **************************************************** -->
1203
+
1204
+ <xsd:complexType name="welcome-file-listType">
1205
+ <xsd:annotation>
1206
+ <xsd:documentation>
1207
+
1208
+ The welcome-file-list contains an ordered list of welcome
1209
+ files elements.
1210
+
1211
+ Used in: web-app
1212
+
1213
+ </xsd:documentation>
1214
+ </xsd:annotation>
1215
+
1216
+ <xsd:sequence>
1217
+ <xsd:element name="welcome-file"
1218
+ type="xsd:string"
1219
+ maxOccurs="unbounded">
1220
+ <xsd:annotation>
1221
+ <xsd:documentation>
1222
+
1223
+ The welcome-file element contains file name to use
1224
+ as a default welcome file, such as index.html
1225
+
1226
+ </xsd:documentation>
1227
+ </xsd:annotation>
1228
+ </xsd:element>
1229
+ </xsd:sequence>
1230
+ <xsd:attribute name="id" type="xsd:ID"/>
1231
+ </xsd:complexType>
1232
+
1233
+ </xsd:schema>
1234
+