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.
- data/COPYRIGHT +33 -0
- data/LICENSE.txt +263 -0
- data/README +12 -0
- data/bin/asadmin +7 -0
- data/bin/asadmin.bat +8 -0
- data/bin/glassfish_rails +40 -0
- data/config/asadminenv.conf +6 -0
- data/config/asenv.bat +28 -0
- data/config/asenv.conf +27 -0
- data/config/glassfish.container +4 -0
- data/domains/domain1/config/admin-keyfile +3 -0
- data/domains/domain1/config/cacerts.jks +0 -0
- data/domains/domain1/config/default-web.xml +906 -0
- data/domains/domain1/config/domain-passwords +0 -0
- data/domains/domain1/config/domain.xml +208 -0
- data/domains/domain1/config/keyfile +6 -0
- data/domains/domain1/config/keystore.jks +0 -0
- data/domains/domain1/config/logging.properties +82 -0
- data/domains/domain1/config/login.conf +18 -0
- data/domains/domain1/config/server.policy +160 -0
- data/domains/domain1/config/sun-acc.xml +40 -0
- data/domains/domain1/config/wss-server-config-1.0.xml +86 -0
- data/domains/domain1/config/wss-server-config-2.0.xml +94 -0
- data/domains/domain1/docroot/favicon.gif +0 -0
- data/domains/domain1/docroot/index.html +87 -0
- data/domains/domain1/master-password +0 -0
- data/lib/appclient/appclientlogin.conf +10 -0
- data/lib/appclient/client.policy +79 -0
- data/lib/appclient/wss-client-config-1.0.xml +84 -0
- data/lib/appclient/wss-client-config-2.0.xml +96 -0
- data/lib/dtds/application-client_1_2.dtd +292 -0
- data/lib/dtds/application-client_1_3.dtd +506 -0
- data/lib/dtds/application_1_2.dtd +197 -0
- data/lib/dtds/application_1_3.dtd +312 -0
- data/lib/dtds/connector_1_0.dtd +561 -0
- data/lib/dtds/ejb-jar_1_1.dtd +894 -0
- data/lib/dtds/ejb-jar_2_0.dtd +1671 -0
- data/lib/dtds/sun-application-client-container_1_0.dtd +123 -0
- data/lib/dtds/sun-application-client-container_1_1.dtd +264 -0
- data/lib/dtds/sun-application-client-container_1_2.dtd +267 -0
- data/lib/dtds/sun-application-client_1_3-0.dtd +57 -0
- data/lib/dtds/sun-application-client_1_4-0.dtd +182 -0
- data/lib/dtds/sun-application-client_1_4-1.dtd +431 -0
- data/lib/dtds/sun-application-client_5_0-0.dtd +495 -0
- data/lib/dtds/sun-application_1_3-0.dtd +30 -0
- data/lib/dtds/sun-application_1_4-0.dtd +44 -0
- data/lib/dtds/sun-application_5_0-0.dtd +51 -0
- data/lib/dtds/sun-cmp-mapping_1_0.dtd +100 -0
- data/lib/dtds/sun-cmp-mapping_1_1.dtd +99 -0
- data/lib/dtds/sun-cmp-mapping_1_2.dtd +106 -0
- data/lib/dtds/sun-connector_1_0-0.dtd +66 -0
- data/lib/dtds/sun-connector_1_5-0.dtd +62 -0
- data/lib/dtds/sun-domain_1_0.dtd +2007 -0
- data/lib/dtds/sun-domain_1_1.dtd +3080 -0
- data/lib/dtds/sun-domain_1_2.dtd +3697 -0
- data/lib/dtds/sun-domain_1_3.dtd +3867 -0
- data/lib/dtds/sun-ejb-jar_2_0-0.dtd +449 -0
- data/lib/dtds/sun-ejb-jar_2_0-1.dtd +454 -0
- data/lib/dtds/sun-ejb-jar_2_1-0.dtd +756 -0
- data/lib/dtds/sun-ejb-jar_2_1-1.dtd +1085 -0
- data/lib/dtds/sun-ejb-jar_3_0-0.dtd +1113 -0
- data/lib/dtds/sun-loadbalancer_1_0.dtd +156 -0
- data/lib/dtds/sun-loadbalancer_1_1.dtd +172 -0
- data/lib/dtds/sun-resources_1_0.dtd +650 -0
- data/lib/dtds/sun-resources_1_1.dtd +650 -0
- data/lib/dtds/sun-resources_1_2.dtd +662 -0
- data/lib/dtds/sun-resources_1_3.dtd +732 -0
- data/lib/dtds/sun-server_1_0.dtd +1056 -0
- data/lib/dtds/sun-web-app_2_3-0.dtd +230 -0
- data/lib/dtds/sun-web-app_2_3-1.dtd +230 -0
- data/lib/dtds/sun-web-app_2_4-0.dtd +466 -0
- data/lib/dtds/sun-web-app_2_4-1.dtd +742 -0
- data/lib/dtds/sun-web-app_2_5-0.dtd +789 -0
- data/lib/dtds/web-app_2_2.dtd +639 -0
- data/lib/dtds/web-app_2_3.dtd +1063 -0
- data/lib/dtds/web-jsptaglibrary_1_1.dtd +265 -0
- data/lib/dtds/web-jsptaglibrary_1_2.dtd +468 -0
- data/lib/package-appclient.xml +185 -0
- data/lib/processLauncher.properties +25 -0
- data/lib/processLauncher.xml +189 -0
- data/lib/schemas/XMLSchema.dtd +402 -0
- data/lib/schemas/application-client_1_4.xsd +267 -0
- data/lib/schemas/application-client_5.xsd +304 -0
- data/lib/schemas/application_1_4.xsd +315 -0
- data/lib/schemas/application_5.xsd +336 -0
- data/lib/schemas/connector_1_5.xsd +1036 -0
- data/lib/schemas/datatypes.dtd +203 -0
- data/lib/schemas/ejb-jar_2_1.xsd +2208 -0
- data/lib/schemas/ejb-jar_3_0.xsd +2706 -0
- data/lib/schemas/j2ee_1_4.xsd +1608 -0
- data/lib/schemas/j2ee_jaxrpc_mapping_1_1.xsd +886 -0
- data/lib/schemas/j2ee_web_services_1_1.xsd +491 -0
- data/lib/schemas/j2ee_web_services_client_1_1.xsd +345 -0
- data/lib/schemas/javaee_5.xsd +2096 -0
- data/lib/schemas/javaee_web_services_1_2.xsd +747 -0
- data/lib/schemas/javaee_web_services_client_1_2.xsd +578 -0
- data/lib/schemas/jax-rpc-ri-config.xsd +416 -0
- data/lib/schemas/jsp_2_0.xsd +308 -0
- data/lib/schemas/jsp_2_1.xsd +343 -0
- data/lib/schemas/orm_1_0.xsd +1516 -0
- data/lib/schemas/persistence_1_0.xsd +260 -0
- data/lib/schemas/web-app_2_4.xsd +1234 -0
- data/lib/schemas/web-app_2_5.xsd +1271 -0
- data/lib/schemas/web-jsptaglibrary_2_0.xsd +1010 -0
- data/lib/schemas/web-jsptaglibrary_2_1.xsd +1144 -0
- data/lib/schemas/xml.xsd +82 -0
- data/modules/admin-cli-10.0-SNAPSHOT.jar +0 -0
- data/modules/auto-depends-0.2-SNAPSHOT.jar +0 -0
- data/modules/cli-framework-10.0-SNAPSHOT.jar +0 -0
- data/modules/common-ee-util-10.0-SNAPSHOT.jar +0 -0
- data/modules/common-util-10.0-SNAPSHOT.jar +0 -0
- data/modules/config-0.2-SNAPSHOT.jar +0 -0
- data/modules/config-api-10.0-SNAPSHOT.jar +0 -0
- data/modules/gf-jruby-connector-10.0-SNAPSHOT.jar +0 -0
- data/modules/glassfish-10.0-SNAPSHOT.jar +0 -0
- data/modules/glassfish-api-10.0-SNAPSHOT.jar +0 -0
- data/modules/glassfish.rb +10 -0
- data/modules/grizzly-framework-1.7.1.jar +0 -0
- data/modules/grizzly-http-1.7.1.jar +0 -0
- data/modules/grizzly-http-utils-1.7.1.jar +0 -0
- data/modules/grizzly-jruby-1.7.0.jar +0 -0
- data/modules/grizzly-jruby-module-1.7.0.jar +0 -0
- data/modules/grizzly-module-1.7.1.jar +0 -0
- data/modules/grizzly-portunif-1.7.1.jar +0 -0
- data/modules/grizzly-rcm-1.7.1.jar +0 -0
- data/modules/hk2-0.2-SNAPSHOT.jar +0 -0
- data/modules/hk2-core-0.2-SNAPSHOT.jar +0 -0
- data/modules/junit-4.3.1.jar +0 -0
- data/modules/kernel-10.0-SNAPSHOT.jar +0 -0
- data/modules/persistence-api-1.0b.jar +0 -0
- data/modules/servlet-api-2.5.jar +0 -0
- data/modules/sjsxp-1.0.jar +0 -0
- data/modules/stax-api-1.0-2.jar +0 -0
- data/modules/tiger-types-1.0.jar +0 -0
- metadata +206 -0
@@ -0,0 +1,1608 @@
|
|
1
|
+
<?xml version="1.0" encoding="UTF-8"?>
|
2
|
+
|
3
|
+
<xsd:schema
|
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="1.4">
|
10
|
+
<xsd:annotation>
|
11
|
+
<xsd:documentation>
|
12
|
+
@(#)j2ee_1_4.xsds 1.43 03/09/16
|
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
|
+
The following definitions that appear in the common
|
55
|
+
shareable schema(s) of J2EE deployment descriptors should be
|
56
|
+
interpreted with respect to the context they are included:
|
57
|
+
|
58
|
+
Deployment Component may indicate one of the following:
|
59
|
+
j2ee application;
|
60
|
+
application client;
|
61
|
+
web application;
|
62
|
+
enterprise bean;
|
63
|
+
resource adapter;
|
64
|
+
|
65
|
+
Deployment File may indicate one of the following:
|
66
|
+
ear file;
|
67
|
+
war file;
|
68
|
+
jar file;
|
69
|
+
rar file;
|
70
|
+
|
71
|
+
</xsd:documentation>
|
72
|
+
</xsd:annotation>
|
73
|
+
|
74
|
+
<xsd:import namespace="http://www.w3.org/XML/1998/namespace"
|
75
|
+
schemaLocation="http://www.w3.org/2001/xml.xsd"/>
|
76
|
+
|
77
|
+
<xsd:include schemaLocation=
|
78
|
+
"http://www.ibm.com/webservices/xsd/j2ee_web_services_client_1_1.xsd"/>
|
79
|
+
|
80
|
+
|
81
|
+
<!-- **************************************************** -->
|
82
|
+
|
83
|
+
<xsd:group name="descriptionGroup">
|
84
|
+
<xsd:annotation>
|
85
|
+
<xsd:documentation>
|
86
|
+
|
87
|
+
This group keeps the usage of the contained description related
|
88
|
+
elements consistent across J2EE deployment descriptors.
|
89
|
+
|
90
|
+
All elements may occur multiple times with different languages,
|
91
|
+
to support localization of the content.
|
92
|
+
|
93
|
+
</xsd:documentation>
|
94
|
+
</xsd:annotation>
|
95
|
+
<xsd:sequence>
|
96
|
+
<xsd:element name="description"
|
97
|
+
type="j2ee:descriptionType"
|
98
|
+
minOccurs="0"
|
99
|
+
maxOccurs="unbounded"/>
|
100
|
+
<xsd:element name="display-name"
|
101
|
+
type="j2ee:display-nameType"
|
102
|
+
minOccurs="0"
|
103
|
+
maxOccurs="unbounded"/>
|
104
|
+
<xsd:element name="icon"
|
105
|
+
type="j2ee:iconType"
|
106
|
+
minOccurs="0"
|
107
|
+
maxOccurs="unbounded"/>
|
108
|
+
</xsd:sequence>
|
109
|
+
</xsd:group>
|
110
|
+
|
111
|
+
<!-- **************************************************** -->
|
112
|
+
|
113
|
+
<xsd:complexType name="descriptionType">
|
114
|
+
<xsd:annotation>
|
115
|
+
<xsd:documentation>
|
116
|
+
|
117
|
+
The description type is used by a description element to
|
118
|
+
provide text describing the parent element. The elements
|
119
|
+
that use this type should include any information that the
|
120
|
+
Deployment Component's Deployment File file producer wants
|
121
|
+
to provide to the consumer of the Deployment Component's
|
122
|
+
Deployment File (i.e., to the Deployer). Typically, the
|
123
|
+
tools used by such a Deployment File consumer will display
|
124
|
+
the description when processing the parent element that
|
125
|
+
contains the description.
|
126
|
+
|
127
|
+
The lang attribute defines the language that the
|
128
|
+
description is provided in. The default value is "en" (English).
|
129
|
+
|
130
|
+
</xsd:documentation>
|
131
|
+
</xsd:annotation>
|
132
|
+
<xsd:simpleContent>
|
133
|
+
<xsd:extension base="j2ee:xsdStringType">
|
134
|
+
<xsd:attribute ref="xml:lang"/>
|
135
|
+
</xsd:extension>
|
136
|
+
</xsd:simpleContent>
|
137
|
+
</xsd:complexType>
|
138
|
+
|
139
|
+
<!-- **************************************************** -->
|
140
|
+
|
141
|
+
<xsd:simpleType name="dewey-versionType">
|
142
|
+
<xsd:annotation>
|
143
|
+
<xsd:documentation>
|
144
|
+
|
145
|
+
This type defines a dewey decimal which is used
|
146
|
+
to describe versions of documents.
|
147
|
+
|
148
|
+
</xsd:documentation>
|
149
|
+
</xsd:annotation>
|
150
|
+
|
151
|
+
<xsd:restriction base="xsd:decimal">
|
152
|
+
<xsd:whiteSpace value="collapse"/>
|
153
|
+
</xsd:restriction>
|
154
|
+
|
155
|
+
</xsd:simpleType>
|
156
|
+
|
157
|
+
<!-- **************************************************** -->
|
158
|
+
|
159
|
+
<xsd:complexType name="display-nameType">
|
160
|
+
<xsd:annotation>
|
161
|
+
<xsd:documentation>
|
162
|
+
<![CDATA[
|
163
|
+
|
164
|
+
The display-name type contains a short name that is intended
|
165
|
+
to be displayed by tools. It is used by display-name
|
166
|
+
elements. The display name need not be unique.
|
167
|
+
|
168
|
+
Example:
|
169
|
+
|
170
|
+
...
|
171
|
+
<display-name xml:lang="en">Employee Self Service</display-name>
|
172
|
+
|
173
|
+
The value of the xml:lang attribute is "en" (English) by default.
|
174
|
+
|
175
|
+
]]>
|
176
|
+
</xsd:documentation>
|
177
|
+
</xsd:annotation>
|
178
|
+
<xsd:simpleContent>
|
179
|
+
<xsd:extension base="j2ee:string">
|
180
|
+
<xsd:attribute ref="xml:lang"/>
|
181
|
+
</xsd:extension>
|
182
|
+
</xsd:simpleContent>
|
183
|
+
</xsd:complexType>
|
184
|
+
|
185
|
+
<!-- **************************************************** -->
|
186
|
+
|
187
|
+
<xsd:complexType name="ejb-linkType">
|
188
|
+
<xsd:annotation>
|
189
|
+
<xsd:documentation>
|
190
|
+
<![CDATA[
|
191
|
+
|
192
|
+
The ejb-linkType is used by ejb-link
|
193
|
+
elements in the ejb-ref or ejb-local-ref elements to specify
|
194
|
+
that an EJB reference is linked to enterprise bean.
|
195
|
+
|
196
|
+
The value of the ejb-link element must be the ejb-name of an
|
197
|
+
enterprise bean in the same ejb-jar file or in another ejb-jar
|
198
|
+
file in the same J2EE application unit.
|
199
|
+
|
200
|
+
Alternatively, the name in the ejb-link element may be
|
201
|
+
composed of a path name specifying the ejb-jar containing the
|
202
|
+
referenced enterprise bean with the ejb-name of the target
|
203
|
+
bean appended and separated from the path name by "#". The
|
204
|
+
path name is relative to the Deployment File containing
|
205
|
+
Deployment Component that is referencing the enterprise
|
206
|
+
bean. This allows multiple enterprise beans with the same
|
207
|
+
ejb-name to be uniquely identified.
|
208
|
+
|
209
|
+
Examples:
|
210
|
+
|
211
|
+
<ejb-link>EmployeeRecord</ejb-link>
|
212
|
+
|
213
|
+
<ejb-link>../products/product.jar#ProductEJB</ejb-link>
|
214
|
+
|
215
|
+
]]>
|
216
|
+
</xsd:documentation>
|
217
|
+
</xsd:annotation>
|
218
|
+
<xsd:simpleContent>
|
219
|
+
<xsd:restriction base="j2ee:string"/>
|
220
|
+
</xsd:simpleContent>
|
221
|
+
</xsd:complexType>
|
222
|
+
|
223
|
+
<!-- **************************************************** -->
|
224
|
+
|
225
|
+
<xsd:complexType name="ejb-local-refType">
|
226
|
+
<xsd:annotation>
|
227
|
+
<xsd:documentation>
|
228
|
+
|
229
|
+
The ejb-local-refType is used by ejb-local-ref elements for
|
230
|
+
the declaration of a reference to an enterprise bean's local
|
231
|
+
home. The declaration consists of:
|
232
|
+
|
233
|
+
- an optional description
|
234
|
+
- the EJB reference name used in the code of the Deployment
|
235
|
+
Component that's referencing the enterprise bean
|
236
|
+
- the expected type of the referenced enterprise bean
|
237
|
+
- the expected local home and local interfaces of the
|
238
|
+
referenced enterprise bean
|
239
|
+
- optional ejb-link information, used to specify the
|
240
|
+
referenced enterprise bean
|
241
|
+
|
242
|
+
</xsd:documentation>
|
243
|
+
</xsd:annotation>
|
244
|
+
|
245
|
+
<xsd:sequence>
|
246
|
+
<xsd:element name="description"
|
247
|
+
type="j2ee:descriptionType"
|
248
|
+
minOccurs="0"
|
249
|
+
maxOccurs="unbounded"/>
|
250
|
+
<xsd:element name="ejb-ref-name"
|
251
|
+
type="j2ee:ejb-ref-nameType"/>
|
252
|
+
<xsd:element name="ejb-ref-type"
|
253
|
+
type="j2ee:ejb-ref-typeType"/>
|
254
|
+
<xsd:element name="local-home"
|
255
|
+
type="j2ee:local-homeType"/>
|
256
|
+
<xsd:element name="local"
|
257
|
+
type="j2ee:localType"/>
|
258
|
+
<xsd:element name="ejb-link"
|
259
|
+
type="j2ee:ejb-linkType"
|
260
|
+
minOccurs="0"/>
|
261
|
+
</xsd:sequence>
|
262
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
263
|
+
</xsd:complexType>
|
264
|
+
|
265
|
+
<!-- **************************************************** -->
|
266
|
+
|
267
|
+
<xsd:complexType name="ejb-ref-nameType">
|
268
|
+
<xsd:annotation>
|
269
|
+
<xsd:documentation>
|
270
|
+
<![CDATA[
|
271
|
+
|
272
|
+
The ejb-ref-name element contains the name of an EJB
|
273
|
+
reference. The EJB reference is an entry in the
|
274
|
+
Deployment Component's environment and is relative to the
|
275
|
+
java:comp/env context. The name must be unique within the
|
276
|
+
Deployment Component.
|
277
|
+
|
278
|
+
It is recommended that name is prefixed with "ejb/".
|
279
|
+
|
280
|
+
Example:
|
281
|
+
|
282
|
+
<ejb-ref-name>ejb/Payroll</ejb-ref-name>
|
283
|
+
|
284
|
+
]]>
|
285
|
+
</xsd:documentation>
|
286
|
+
</xsd:annotation>
|
287
|
+
<xsd:simpleContent>
|
288
|
+
<xsd:restriction base="j2ee:jndi-nameType"/>
|
289
|
+
</xsd:simpleContent>
|
290
|
+
</xsd:complexType>
|
291
|
+
|
292
|
+
<!-- **************************************************** -->
|
293
|
+
|
294
|
+
<xsd:complexType name="ejb-ref-typeType">
|
295
|
+
<xsd:annotation>
|
296
|
+
<xsd:documentation>
|
297
|
+
|
298
|
+
The ejb-ref-typeType contains the expected type of the
|
299
|
+
referenced enterprise bean.
|
300
|
+
|
301
|
+
The ejb-ref-type designates a value
|
302
|
+
that must be one of the following:
|
303
|
+
|
304
|
+
Entity
|
305
|
+
Session
|
306
|
+
|
307
|
+
</xsd:documentation>
|
308
|
+
</xsd:annotation>
|
309
|
+
<xsd:simpleContent>
|
310
|
+
<xsd:restriction base="j2ee:string">
|
311
|
+
<xsd:enumeration value="Entity"/>
|
312
|
+
<xsd:enumeration value="Session"/>
|
313
|
+
</xsd:restriction>
|
314
|
+
</xsd:simpleContent>
|
315
|
+
</xsd:complexType>
|
316
|
+
|
317
|
+
<!-- **************************************************** -->
|
318
|
+
|
319
|
+
<xsd:complexType name="ejb-refType">
|
320
|
+
<xsd:annotation>
|
321
|
+
<xsd:documentation>
|
322
|
+
|
323
|
+
The ejb-refType is used by ejb-ref elements for the
|
324
|
+
declaration of a reference to an enterprise bean's home. The
|
325
|
+
declaration consists of:
|
326
|
+
|
327
|
+
- an optional description
|
328
|
+
- the EJB reference name used in the code of
|
329
|
+
the Deployment Component that's referencing the enterprise
|
330
|
+
bean
|
331
|
+
- the expected type of the referenced enterprise bean
|
332
|
+
- the expected home and remote interfaces of the referenced
|
333
|
+
enterprise bean
|
334
|
+
- optional ejb-link information, used to specify the
|
335
|
+
referenced enterprise bean
|
336
|
+
|
337
|
+
</xsd:documentation>
|
338
|
+
</xsd:annotation>
|
339
|
+
|
340
|
+
<xsd:sequence>
|
341
|
+
<xsd:element name="description"
|
342
|
+
type="j2ee:descriptionType"
|
343
|
+
minOccurs="0"
|
344
|
+
maxOccurs="unbounded"/>
|
345
|
+
<xsd:element name="ejb-ref-name"
|
346
|
+
type="j2ee:ejb-ref-nameType"/>
|
347
|
+
<xsd:element name="ejb-ref-type"
|
348
|
+
type="j2ee:ejb-ref-typeType"/>
|
349
|
+
|
350
|
+
<xsd:element name="home"
|
351
|
+
type="j2ee:homeType"/>
|
352
|
+
<xsd:element name="remote"
|
353
|
+
type="j2ee:remoteType"/>
|
354
|
+
<xsd:element name="ejb-link"
|
355
|
+
type="j2ee:ejb-linkType"
|
356
|
+
minOccurs="0"/>
|
357
|
+
</xsd:sequence>
|
358
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
359
|
+
</xsd:complexType>
|
360
|
+
|
361
|
+
<!-- **************************************************** -->
|
362
|
+
|
363
|
+
<xsd:complexType name="emptyType">
|
364
|
+
<xsd:annotation>
|
365
|
+
<xsd:documentation>
|
366
|
+
|
367
|
+
This type is used to designate an empty
|
368
|
+
element when used.
|
369
|
+
|
370
|
+
</xsd:documentation>
|
371
|
+
</xsd:annotation>
|
372
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
373
|
+
</xsd:complexType>
|
374
|
+
|
375
|
+
<!-- **************************************************** -->
|
376
|
+
|
377
|
+
<xsd:complexType name="env-entry-type-valuesType">
|
378
|
+
<xsd:annotation>
|
379
|
+
<xsd:documentation>
|
380
|
+
<![CDATA[
|
381
|
+
|
382
|
+
This type contains the fully-qualified Java type of the
|
383
|
+
environment entry value that is expected by the
|
384
|
+
application's code.
|
385
|
+
|
386
|
+
The following are the legal values of env-entry-type-valuesType:
|
387
|
+
|
388
|
+
java.lang.Boolean
|
389
|
+
java.lang.Byte
|
390
|
+
java.lang.Character
|
391
|
+
java.lang.String
|
392
|
+
java.lang.Short
|
393
|
+
java.lang.Integer
|
394
|
+
java.lang.Long
|
395
|
+
java.lang.Float
|
396
|
+
java.lang.Double
|
397
|
+
|
398
|
+
Example:
|
399
|
+
|
400
|
+
<env-entry-type>java.lang.Boolean</env-entry-type>
|
401
|
+
|
402
|
+
]]>
|
403
|
+
</xsd:documentation>
|
404
|
+
</xsd:annotation>
|
405
|
+
<xsd:simpleContent>
|
406
|
+
<xsd:restriction base="j2ee:string">
|
407
|
+
<xsd:enumeration value="java.lang.Boolean"/>
|
408
|
+
<xsd:enumeration value="java.lang.Byte"/>
|
409
|
+
<xsd:enumeration value="java.lang.Character"/>
|
410
|
+
<xsd:enumeration value="java.lang.String"/>
|
411
|
+
<xsd:enumeration value="java.lang.Short"/>
|
412
|
+
<xsd:enumeration value="java.lang.Integer"/>
|
413
|
+
<xsd:enumeration value="java.lang.Long"/>
|
414
|
+
<xsd:enumeration value="java.lang.Float"/>
|
415
|
+
<xsd:enumeration value="java.lang.Double"/>
|
416
|
+
</xsd:restriction>
|
417
|
+
</xsd:simpleContent>
|
418
|
+
</xsd:complexType>
|
419
|
+
|
420
|
+
<!-- **************************************************** -->
|
421
|
+
|
422
|
+
<xsd:complexType name="env-entryType">
|
423
|
+
<xsd:annotation>
|
424
|
+
<xsd:documentation>
|
425
|
+
|
426
|
+
The env-entryType is used to declare an application's
|
427
|
+
environment entry. The declaration consists of an optional
|
428
|
+
description, the name of the environment entry, and an
|
429
|
+
optional value. If a value is not specified, one must be
|
430
|
+
supplied during deployment.
|
431
|
+
|
432
|
+
It is used by env-entry elements.
|
433
|
+
|
434
|
+
</xsd:documentation>
|
435
|
+
</xsd:annotation>
|
436
|
+
|
437
|
+
<xsd:sequence>
|
438
|
+
<xsd:element name="description"
|
439
|
+
type="j2ee:descriptionType"
|
440
|
+
minOccurs="0"
|
441
|
+
maxOccurs="unbounded"/>
|
442
|
+
<xsd:element name="env-entry-name"
|
443
|
+
type="j2ee:jndi-nameType">
|
444
|
+
<xsd:annotation>
|
445
|
+
<xsd:documentation>
|
446
|
+
<![CDATA[
|
447
|
+
|
448
|
+
The env-entry-name element contains the name of a
|
449
|
+
Deployment Component's environment entry. The name
|
450
|
+
is a JNDI name relative to the java:comp/env
|
451
|
+
context. The name must be unique within a
|
452
|
+
Deployment Component. The uniqueness
|
453
|
+
constraints must be defined within the declared
|
454
|
+
context.
|
455
|
+
|
456
|
+
Example:
|
457
|
+
|
458
|
+
<env-entry-name>minAmount</env-entry-name>
|
459
|
+
|
460
|
+
]]>
|
461
|
+
</xsd:documentation>
|
462
|
+
</xsd:annotation>
|
463
|
+
</xsd:element>
|
464
|
+
|
465
|
+
<xsd:element name="env-entry-type"
|
466
|
+
type="j2ee:env-entry-type-valuesType"/>
|
467
|
+
|
468
|
+
<xsd:element name="env-entry-value"
|
469
|
+
type="j2ee:xsdStringType"
|
470
|
+
minOccurs="0">
|
471
|
+
<xsd:annotation>
|
472
|
+
<xsd:documentation>
|
473
|
+
<![CDATA[
|
474
|
+
|
475
|
+
The env-entry-value designates the value of a
|
476
|
+
Deployment Component's environment entry. The value
|
477
|
+
must be a String that is valid for the
|
478
|
+
constructor of the specified type that takes a
|
479
|
+
single String parameter, or for java.lang.Character,
|
480
|
+
a single character.
|
481
|
+
|
482
|
+
Example:
|
483
|
+
|
484
|
+
<env-entry-value>100.00</env-entry-value>
|
485
|
+
|
486
|
+
]]>
|
487
|
+
</xsd:documentation>
|
488
|
+
</xsd:annotation>
|
489
|
+
</xsd:element>
|
490
|
+
|
491
|
+
</xsd:sequence>
|
492
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
493
|
+
</xsd:complexType>
|
494
|
+
|
495
|
+
<!-- **************************************************** -->
|
496
|
+
|
497
|
+
<xsd:complexType name="fully-qualified-classType">
|
498
|
+
<xsd:annotation>
|
499
|
+
<xsd:documentation>
|
500
|
+
|
501
|
+
The elements that use this type designate the name of a
|
502
|
+
Java class or interface. The name is in the form of a
|
503
|
+
"binary name", as defined in the JLS. This is the form
|
504
|
+
of name used in Class.forName(). Tools that need the
|
505
|
+
canonical name (the name used in source code) will need
|
506
|
+
to convert this binary name to the canonical name.
|
507
|
+
|
508
|
+
</xsd:documentation>
|
509
|
+
</xsd:annotation>
|
510
|
+
<xsd:simpleContent>
|
511
|
+
<xsd:restriction base="j2ee:string"/>
|
512
|
+
</xsd:simpleContent>
|
513
|
+
</xsd:complexType>
|
514
|
+
|
515
|
+
<!-- **************************************************** -->
|
516
|
+
|
517
|
+
<xsd:complexType name="generic-booleanType">
|
518
|
+
<xsd:annotation>
|
519
|
+
<xsd:documentation>
|
520
|
+
|
521
|
+
This type defines four different values which can designate
|
522
|
+
boolean values. This includes values yes and no which are
|
523
|
+
not designated by xsd:boolean
|
524
|
+
|
525
|
+
</xsd:documentation>
|
526
|
+
</xsd:annotation>
|
527
|
+
<xsd:simpleContent>
|
528
|
+
<xsd:restriction base="j2ee:string">
|
529
|
+
<xsd:enumeration value="true"/>
|
530
|
+
<xsd:enumeration value="false"/>
|
531
|
+
<xsd:enumeration value="yes"/>
|
532
|
+
<xsd:enumeration value="no"/>
|
533
|
+
</xsd:restriction>
|
534
|
+
</xsd:simpleContent>
|
535
|
+
</xsd:complexType>
|
536
|
+
|
537
|
+
<!-- **************************************************** -->
|
538
|
+
|
539
|
+
<xsd:complexType name="homeType">
|
540
|
+
<xsd:annotation>
|
541
|
+
<xsd:documentation>
|
542
|
+
<![CDATA[
|
543
|
+
|
544
|
+
The homeType defines the fully-qualified name of
|
545
|
+
an enterprise bean's home interface.
|
546
|
+
|
547
|
+
Example:
|
548
|
+
|
549
|
+
<home>com.aardvark.payroll.PayrollHome</home>
|
550
|
+
|
551
|
+
]]>
|
552
|
+
</xsd:documentation>
|
553
|
+
</xsd:annotation>
|
554
|
+
<xsd:simpleContent>
|
555
|
+
<xsd:restriction base="j2ee:fully-qualified-classType"/>
|
556
|
+
</xsd:simpleContent>
|
557
|
+
</xsd:complexType>
|
558
|
+
|
559
|
+
<!-- **************************************************** -->
|
560
|
+
|
561
|
+
<xsd:complexType name="iconType">
|
562
|
+
<xsd:annotation>
|
563
|
+
<xsd:documentation>
|
564
|
+
|
565
|
+
The icon type contains small-icon and large-icon elements
|
566
|
+
that specify the file names for small and large GIF or
|
567
|
+
JPEG icon images used to represent the parent element in a
|
568
|
+
GUI tool.
|
569
|
+
|
570
|
+
The xml:lang attribute defines the language that the
|
571
|
+
icon file names are provided in. Its value is "en" (English)
|
572
|
+
by default.
|
573
|
+
|
574
|
+
</xsd:documentation>
|
575
|
+
</xsd:annotation>
|
576
|
+
|
577
|
+
<xsd:sequence>
|
578
|
+
<xsd:element name="small-icon" type="j2ee:pathType"
|
579
|
+
minOccurs="0">
|
580
|
+
<xsd:annotation>
|
581
|
+
<xsd:documentation>
|
582
|
+
<![CDATA[
|
583
|
+
|
584
|
+
The small-icon element contains the name of a file
|
585
|
+
containing a small (16 x 16) icon image. The file
|
586
|
+
name is a relative path within the Deployment
|
587
|
+
Component's Deployment File.
|
588
|
+
|
589
|
+
The image may be either in the JPEG or GIF format.
|
590
|
+
The icon can be used by tools.
|
591
|
+
|
592
|
+
Example:
|
593
|
+
|
594
|
+
<small-icon>employee-service-icon16x16.jpg</small-icon>
|
595
|
+
|
596
|
+
]]>
|
597
|
+
</xsd:documentation>
|
598
|
+
</xsd:annotation>
|
599
|
+
</xsd:element>
|
600
|
+
<xsd:element name="large-icon" type="j2ee:pathType"
|
601
|
+
minOccurs="0">
|
602
|
+
<xsd:annotation>
|
603
|
+
<xsd:documentation>
|
604
|
+
<![CDATA[
|
605
|
+
|
606
|
+
The large-icon element contains the name of a file
|
607
|
+
containing a large
|
608
|
+
(32 x 32) icon image. The file name is a relative
|
609
|
+
path within the Deployment Component's Deployment
|
610
|
+
File.
|
611
|
+
|
612
|
+
The image may be either in the JPEG or GIF format.
|
613
|
+
The icon can be used by tools.
|
614
|
+
|
615
|
+
Example:
|
616
|
+
|
617
|
+
<large-icon>employee-service-icon32x32.jpg</large-icon>
|
618
|
+
|
619
|
+
]]>
|
620
|
+
</xsd:documentation>
|
621
|
+
</xsd:annotation>
|
622
|
+
</xsd:element>
|
623
|
+
|
624
|
+
</xsd:sequence>
|
625
|
+
|
626
|
+
<xsd:attribute ref="xml:lang"/>
|
627
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
628
|
+
|
629
|
+
</xsd:complexType>
|
630
|
+
|
631
|
+
<!-- **************************************************** -->
|
632
|
+
|
633
|
+
<xsd:complexType name="java-identifierType">
|
634
|
+
<xsd:annotation>
|
635
|
+
<xsd:documentation>
|
636
|
+
|
637
|
+
The java-identifierType defines a Java identifier.
|
638
|
+
The users of this type should further verify that
|
639
|
+
the content does not contain Java reserved keywords.
|
640
|
+
|
641
|
+
</xsd:documentation>
|
642
|
+
</xsd:annotation>
|
643
|
+
<xsd:simpleContent>
|
644
|
+
<xsd:restriction base="j2ee:string">
|
645
|
+
<xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/>
|
646
|
+
</xsd:restriction>
|
647
|
+
</xsd:simpleContent>
|
648
|
+
</xsd:complexType>
|
649
|
+
|
650
|
+
<!-- **************************************************** -->
|
651
|
+
|
652
|
+
<xsd:complexType name="java-typeType">
|
653
|
+
<xsd:annotation>
|
654
|
+
<xsd:documentation>
|
655
|
+
|
656
|
+
This is a generic type that designates a Java primitive
|
657
|
+
type or a fully qualified name of a Java interface/type,
|
658
|
+
or an array of such types.
|
659
|
+
|
660
|
+
</xsd:documentation>
|
661
|
+
</xsd:annotation>
|
662
|
+
<xsd:simpleContent>
|
663
|
+
<xsd:restriction base="j2ee:string">
|
664
|
+
<xsd:pattern value="[^\p{Z}]*"/>
|
665
|
+
</xsd:restriction>
|
666
|
+
</xsd:simpleContent>
|
667
|
+
</xsd:complexType>
|
668
|
+
|
669
|
+
<!-- **************************************************** -->
|
670
|
+
|
671
|
+
<xsd:complexType name="jndi-nameType">
|
672
|
+
<xsd:annotation>
|
673
|
+
<xsd:documentation>
|
674
|
+
|
675
|
+
The jndi-nameType type designates a JNDI name in the
|
676
|
+
Deployment Component's environment and is relative to the
|
677
|
+
java:comp/env context. A JNDI name must be unique within the
|
678
|
+
Deployment Component.
|
679
|
+
|
680
|
+
</xsd:documentation>
|
681
|
+
</xsd:annotation>
|
682
|
+
<xsd:simpleContent>
|
683
|
+
<xsd:restriction base="j2ee:string"/>
|
684
|
+
</xsd:simpleContent>
|
685
|
+
</xsd:complexType>
|
686
|
+
|
687
|
+
<!-- **************************************************** -->
|
688
|
+
|
689
|
+
<xsd:group name="jndiEnvironmentRefsGroup">
|
690
|
+
<xsd:annotation>
|
691
|
+
<xsd:documentation>
|
692
|
+
|
693
|
+
This group keeps the usage of the contained JNDI environment
|
694
|
+
reference elements consistent across J2EE deployment descriptors.
|
695
|
+
|
696
|
+
</xsd:documentation>
|
697
|
+
</xsd:annotation>
|
698
|
+
<xsd:sequence>
|
699
|
+
<xsd:element name="env-entry"
|
700
|
+
type="j2ee:env-entryType"
|
701
|
+
minOccurs="0" maxOccurs="unbounded"/>
|
702
|
+
<xsd:element name="ejb-ref"
|
703
|
+
type="j2ee:ejb-refType"
|
704
|
+
minOccurs="0" maxOccurs="unbounded"/>
|
705
|
+
<xsd:element name="ejb-local-ref"
|
706
|
+
type="j2ee:ejb-local-refType"
|
707
|
+
minOccurs="0" maxOccurs="unbounded"/>
|
708
|
+
<xsd:group ref="j2ee:service-refGroup"/>
|
709
|
+
<xsd:element name="resource-ref"
|
710
|
+
type="j2ee:resource-refType"
|
711
|
+
minOccurs="0" maxOccurs="unbounded"/>
|
712
|
+
<xsd:element name="resource-env-ref"
|
713
|
+
type="j2ee:resource-env-refType"
|
714
|
+
minOccurs="0" maxOccurs="unbounded"/>
|
715
|
+
<xsd:element name="message-destination-ref"
|
716
|
+
type="j2ee:message-destination-refType"
|
717
|
+
minOccurs="0" maxOccurs="unbounded"/>
|
718
|
+
</xsd:sequence>
|
719
|
+
</xsd:group>
|
720
|
+
|
721
|
+
<!-- **************************************************** -->
|
722
|
+
|
723
|
+
<xsd:complexType name="listenerType">
|
724
|
+
<xsd:annotation>
|
725
|
+
<xsd:documentation>
|
726
|
+
|
727
|
+
The listenerType indicates the deployment properties for a web
|
728
|
+
application listener bean.
|
729
|
+
|
730
|
+
</xsd:documentation>
|
731
|
+
</xsd:annotation>
|
732
|
+
|
733
|
+
<xsd:sequence>
|
734
|
+
<xsd:group ref="j2ee:descriptionGroup"/>
|
735
|
+
<xsd:element name="listener-class"
|
736
|
+
type="j2ee:fully-qualified-classType">
|
737
|
+
<xsd:annotation>
|
738
|
+
<xsd:documentation>
|
739
|
+
|
740
|
+
The listener-class element declares a class in the
|
741
|
+
application must be registered as a web
|
742
|
+
application listener bean. The value is the fully
|
743
|
+
qualified classname of the listener class.
|
744
|
+
|
745
|
+
</xsd:documentation>
|
746
|
+
</xsd:annotation>
|
747
|
+
</xsd:element>
|
748
|
+
</xsd:sequence>
|
749
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
750
|
+
</xsd:complexType>
|
751
|
+
|
752
|
+
<!-- **************************************************** -->
|
753
|
+
|
754
|
+
<xsd:complexType name="local-homeType">
|
755
|
+
<xsd:annotation>
|
756
|
+
<xsd:documentation>
|
757
|
+
|
758
|
+
The local-homeType defines the fully-qualified
|
759
|
+
name of an enterprise bean's local home interface.
|
760
|
+
|
761
|
+
</xsd:documentation>
|
762
|
+
</xsd:annotation>
|
763
|
+
<xsd:simpleContent>
|
764
|
+
<xsd:restriction base="j2ee:fully-qualified-classType"/>
|
765
|
+
</xsd:simpleContent>
|
766
|
+
</xsd:complexType>
|
767
|
+
|
768
|
+
<!-- **************************************************** -->
|
769
|
+
|
770
|
+
<xsd:complexType name="localType">
|
771
|
+
<xsd:annotation>
|
772
|
+
<xsd:documentation>
|
773
|
+
|
774
|
+
The localType defines the fully-qualified name of an
|
775
|
+
enterprise bean's local interface.
|
776
|
+
|
777
|
+
</xsd:documentation>
|
778
|
+
</xsd:annotation>
|
779
|
+
<xsd:simpleContent>
|
780
|
+
<xsd:restriction base="j2ee:fully-qualified-classType"/>
|
781
|
+
</xsd:simpleContent>
|
782
|
+
</xsd:complexType>
|
783
|
+
|
784
|
+
<!-- **************************************************** -->
|
785
|
+
|
786
|
+
<xsd:complexType name="message-destination-linkType">
|
787
|
+
<xsd:annotation>
|
788
|
+
<xsd:documentation>
|
789
|
+
|
790
|
+
The message-destination-linkType is used to link a message
|
791
|
+
destination reference or message-driven bean to a message
|
792
|
+
destination.
|
793
|
+
|
794
|
+
The Assembler sets the value to reflect the flow of messages
|
795
|
+
between producers and consumers in the application.
|
796
|
+
|
797
|
+
The value must be the message-destination-name of a message
|
798
|
+
destination in the same Deployment File or in another
|
799
|
+
Deployment File in the same J2EE application unit.
|
800
|
+
|
801
|
+
Alternatively, the value may be composed of a path name
|
802
|
+
specifying a Deployment File containing the referenced
|
803
|
+
message destination with the message-destination-name of the
|
804
|
+
destination appended and separated from the path name by
|
805
|
+
"#". The path name is relative to the Deployment File
|
806
|
+
containing Deployment Component that is referencing the
|
807
|
+
message destination. This allows multiple message
|
808
|
+
destinations with the same name to be uniquely identified.
|
809
|
+
|
810
|
+
</xsd:documentation>
|
811
|
+
</xsd:annotation>
|
812
|
+
<xsd:simpleContent>
|
813
|
+
<xsd:restriction base="j2ee:string"/>
|
814
|
+
</xsd:simpleContent>
|
815
|
+
</xsd:complexType>
|
816
|
+
|
817
|
+
<!-- **************************************************** -->
|
818
|
+
|
819
|
+
<xsd:complexType name="message-destination-refType">
|
820
|
+
<xsd:annotation>
|
821
|
+
<xsd:documentation>
|
822
|
+
<![CDATA[
|
823
|
+
|
824
|
+
The message-destination-ref element contains a declaration
|
825
|
+
of Deployment Component's reference to a message destination
|
826
|
+
associated with a resource in Deployment Component's
|
827
|
+
environment. It consists of:
|
828
|
+
|
829
|
+
- an optional description
|
830
|
+
- the message destination reference name
|
831
|
+
- the message destination type
|
832
|
+
- a specification as to whether the
|
833
|
+
destination is used for
|
834
|
+
consuming or producing messages, or both
|
835
|
+
- a link to the message destination
|
836
|
+
|
837
|
+
Examples:
|
838
|
+
|
839
|
+
<message-destination-ref>
|
840
|
+
<message-destination-ref-name>jms/StockQueue
|
841
|
+
</message-destination-ref-name>
|
842
|
+
<message-destination-type>javax.jms.Queue
|
843
|
+
</message-destination-type>
|
844
|
+
<message-destination-usage>Consumes
|
845
|
+
</message-destination-usage>
|
846
|
+
<message-destination-link>CorporateStocks
|
847
|
+
</message-destination-link>
|
848
|
+
</message-destination-ref>
|
849
|
+
|
850
|
+
]]>
|
851
|
+
</xsd:documentation>
|
852
|
+
</xsd:annotation>
|
853
|
+
<xsd:sequence>
|
854
|
+
<xsd:element name="description"
|
855
|
+
type="j2ee:descriptionType"
|
856
|
+
minOccurs="0"
|
857
|
+
maxOccurs="unbounded"/>
|
858
|
+
<xsd:element name="message-destination-ref-name"
|
859
|
+
type="j2ee:jndi-nameType">
|
860
|
+
<xsd:annotation>
|
861
|
+
<xsd:documentation>
|
862
|
+
|
863
|
+
The message-destination-ref-name element specifies
|
864
|
+
the name of a message destination reference; its
|
865
|
+
value is the environment entry name used in
|
866
|
+
Deployment Component code. The name is a JNDI name
|
867
|
+
relative to the java:comp/env context and must be
|
868
|
+
unique within an ejb-jar (for enterprise beans) or a
|
869
|
+
Deployment File (for others).
|
870
|
+
|
871
|
+
</xsd:documentation>
|
872
|
+
</xsd:annotation>
|
873
|
+
</xsd:element>
|
874
|
+
<xsd:element name="message-destination-type"
|
875
|
+
type="j2ee:message-destination-typeType"/>
|
876
|
+
<xsd:element name="message-destination-usage"
|
877
|
+
type="j2ee:message-destination-usageType"/>
|
878
|
+
<xsd:element name="message-destination-link"
|
879
|
+
type="j2ee:message-destination-linkType"
|
880
|
+
minOccurs="0"/>
|
881
|
+
</xsd:sequence>
|
882
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
883
|
+
|
884
|
+
</xsd:complexType>
|
885
|
+
|
886
|
+
<!-- **************************************************** -->
|
887
|
+
|
888
|
+
<xsd:complexType name="message-destination-typeType">
|
889
|
+
<xsd:annotation>
|
890
|
+
<xsd:documentation>
|
891
|
+
<![CDATA[
|
892
|
+
|
893
|
+
The message-destination-typeType specifies the type of
|
894
|
+
the destination. The type is specified by the Java interface
|
895
|
+
expected to be implemented by the destination.
|
896
|
+
|
897
|
+
Example:
|
898
|
+
|
899
|
+
<message-destination-type>javax.jms.Queue
|
900
|
+
</message-destination-type>
|
901
|
+
|
902
|
+
]]>
|
903
|
+
</xsd:documentation>
|
904
|
+
</xsd:annotation>
|
905
|
+
<xsd:simpleContent>
|
906
|
+
<xsd:restriction base="j2ee:fully-qualified-classType"/>
|
907
|
+
</xsd:simpleContent>
|
908
|
+
</xsd:complexType>
|
909
|
+
|
910
|
+
<!-- **************************************************** -->
|
911
|
+
|
912
|
+
<xsd:complexType name="message-destination-usageType">
|
913
|
+
<xsd:annotation>
|
914
|
+
<xsd:documentation>
|
915
|
+
|
916
|
+
The message-destination-usageType specifies the use of the
|
917
|
+
message destination indicated by the reference. The value
|
918
|
+
indicates whether messages are consumed from the message
|
919
|
+
destination, produced for the destination, or both. The
|
920
|
+
Assembler makes use of this information in linking producers
|
921
|
+
of a destination with its consumers.
|
922
|
+
|
923
|
+
The value of the message-destination-usage element must be
|
924
|
+
one of the following:
|
925
|
+
Consumes
|
926
|
+
Produces
|
927
|
+
ConsumesProduces
|
928
|
+
|
929
|
+
</xsd:documentation>
|
930
|
+
</xsd:annotation>
|
931
|
+
<xsd:simpleContent>
|
932
|
+
<xsd:restriction base="j2ee:string">
|
933
|
+
<xsd:enumeration value="Consumes"/>
|
934
|
+
<xsd:enumeration value="Produces"/>
|
935
|
+
<xsd:enumeration value="ConsumesProduces"/>
|
936
|
+
</xsd:restriction>
|
937
|
+
</xsd:simpleContent>
|
938
|
+
</xsd:complexType>
|
939
|
+
|
940
|
+
<!-- **************************************************** -->
|
941
|
+
|
942
|
+
<xsd:complexType name="message-destinationType">
|
943
|
+
<xsd:annotation>
|
944
|
+
<xsd:documentation>
|
945
|
+
<![CDATA[
|
946
|
+
|
947
|
+
The message-destinationType specifies a message
|
948
|
+
destination. The logical destination described by this
|
949
|
+
element is mapped to a physical destination by the Deployer.
|
950
|
+
|
951
|
+
The message destination element contains:
|
952
|
+
|
953
|
+
- an optional description
|
954
|
+
- an optional display-name
|
955
|
+
- an optional icon
|
956
|
+
- a message destination name which must be unique
|
957
|
+
among message destination names within the same
|
958
|
+
Deployment File.
|
959
|
+
|
960
|
+
Example:
|
961
|
+
|
962
|
+
<message-destination>
|
963
|
+
<message-destination-name>CorporateStocks
|
964
|
+
</message-destination-name>
|
965
|
+
</message-destination>
|
966
|
+
|
967
|
+
]]>
|
968
|
+
</xsd:documentation>
|
969
|
+
</xsd:annotation>
|
970
|
+
<xsd:sequence>
|
971
|
+
<xsd:group ref="j2ee:descriptionGroup"/>
|
972
|
+
<xsd:element name="message-destination-name"
|
973
|
+
type="j2ee:string">
|
974
|
+
<xsd:annotation>
|
975
|
+
<xsd:documentation>
|
976
|
+
|
977
|
+
The message-destination-name element specifies a
|
978
|
+
name for a message destination. This name must be
|
979
|
+
unique among the names of message destinations
|
980
|
+
within the Deployment File.
|
981
|
+
|
982
|
+
</xsd:documentation>
|
983
|
+
</xsd:annotation>
|
984
|
+
</xsd:element>
|
985
|
+
</xsd:sequence>
|
986
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
987
|
+
</xsd:complexType>
|
988
|
+
|
989
|
+
<!-- **************************************************** -->
|
990
|
+
|
991
|
+
<xsd:complexType name="param-valueType">
|
992
|
+
<xsd:annotation>
|
993
|
+
<xsd:documentation>
|
994
|
+
|
995
|
+
This type is a general type that can be used to declare
|
996
|
+
parameter/value lists.
|
997
|
+
|
998
|
+
</xsd:documentation>
|
999
|
+
</xsd:annotation>
|
1000
|
+
|
1001
|
+
<xsd:sequence>
|
1002
|
+
<xsd:element name="description"
|
1003
|
+
type="j2ee:descriptionType"
|
1004
|
+
minOccurs="0"
|
1005
|
+
maxOccurs="unbounded"/>
|
1006
|
+
<xsd:element name="param-name"
|
1007
|
+
type="j2ee:string">
|
1008
|
+
<xsd:annotation>
|
1009
|
+
<xsd:documentation>
|
1010
|
+
|
1011
|
+
The param-name element contains the name of a
|
1012
|
+
parameter.
|
1013
|
+
|
1014
|
+
</xsd:documentation>
|
1015
|
+
</xsd:annotation>
|
1016
|
+
</xsd:element>
|
1017
|
+
|
1018
|
+
<xsd:element name="param-value"
|
1019
|
+
type="j2ee:xsdStringType">
|
1020
|
+
<xsd:annotation>
|
1021
|
+
<xsd:documentation>
|
1022
|
+
|
1023
|
+
The param-value element contains the value of a
|
1024
|
+
parameter.
|
1025
|
+
|
1026
|
+
</xsd:documentation>
|
1027
|
+
</xsd:annotation>
|
1028
|
+
</xsd:element>
|
1029
|
+
</xsd:sequence>
|
1030
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
1031
|
+
</xsd:complexType>
|
1032
|
+
|
1033
|
+
<!-- **************************************************** -->
|
1034
|
+
|
1035
|
+
<xsd:complexType name="pathType">
|
1036
|
+
<xsd:annotation>
|
1037
|
+
<xsd:documentation>
|
1038
|
+
|
1039
|
+
The elements that use this type designate either a relative
|
1040
|
+
path or an absolute path starting with a "/".
|
1041
|
+
|
1042
|
+
In elements that specify a pathname to a file within the
|
1043
|
+
same Deployment File, relative filenames (i.e., those not
|
1044
|
+
starting with "/") are considered relative to the root of
|
1045
|
+
the Deployment File's namespace. Absolute filenames (i.e.,
|
1046
|
+
those starting with "/") also specify names in the root of
|
1047
|
+
the Deployment File's namespace. In general, relative names
|
1048
|
+
are preferred. The exception is .war files where absolute
|
1049
|
+
names are preferred for consistency with the Servlet API.
|
1050
|
+
|
1051
|
+
</xsd:documentation>
|
1052
|
+
</xsd:annotation>
|
1053
|
+
<xsd:simpleContent>
|
1054
|
+
<xsd:restriction base="j2ee:string"/>
|
1055
|
+
</xsd:simpleContent>
|
1056
|
+
</xsd:complexType>
|
1057
|
+
|
1058
|
+
<!-- **************************************************** -->
|
1059
|
+
|
1060
|
+
<xsd:complexType name="remoteType">
|
1061
|
+
<xsd:annotation>
|
1062
|
+
<xsd:documentation>
|
1063
|
+
<![CDATA[
|
1064
|
+
|
1065
|
+
The remote element contains the fully-qualified name
|
1066
|
+
of the enterprise bean's remote interface.
|
1067
|
+
|
1068
|
+
Example:
|
1069
|
+
|
1070
|
+
<remote>com.wombat.empl.EmployeeService</remote>
|
1071
|
+
|
1072
|
+
]]>
|
1073
|
+
</xsd:documentation>
|
1074
|
+
</xsd:annotation>
|
1075
|
+
<xsd:simpleContent>
|
1076
|
+
<xsd:restriction base="j2ee:fully-qualified-classType"/>
|
1077
|
+
</xsd:simpleContent>
|
1078
|
+
</xsd:complexType>
|
1079
|
+
|
1080
|
+
<!-- **************************************************** -->
|
1081
|
+
|
1082
|
+
<xsd:complexType name="res-authType">
|
1083
|
+
<xsd:annotation>
|
1084
|
+
<xsd:documentation>
|
1085
|
+
|
1086
|
+
The res-authType specifies whether the Deployment Component
|
1087
|
+
code signs on programmatically to the resource manager, or
|
1088
|
+
whether the Container will sign on to the resource manager
|
1089
|
+
on behalf of the Deployment Component. In the latter case,
|
1090
|
+
the Container uses information that is supplied by the
|
1091
|
+
Deployer.
|
1092
|
+
|
1093
|
+
The value must be one of the two following:
|
1094
|
+
|
1095
|
+
Application
|
1096
|
+
Container
|
1097
|
+
|
1098
|
+
</xsd:documentation>
|
1099
|
+
</xsd:annotation>
|
1100
|
+
<xsd:simpleContent>
|
1101
|
+
<xsd:restriction base="j2ee:string">
|
1102
|
+
<xsd:enumeration value="Application"/>
|
1103
|
+
<xsd:enumeration value="Container"/>
|
1104
|
+
</xsd:restriction>
|
1105
|
+
</xsd:simpleContent>
|
1106
|
+
</xsd:complexType>
|
1107
|
+
|
1108
|
+
<!-- **************************************************** -->
|
1109
|
+
|
1110
|
+
<xsd:complexType name="res-sharing-scopeType">
|
1111
|
+
<xsd:annotation>
|
1112
|
+
<xsd:documentation>
|
1113
|
+
|
1114
|
+
The res-sharing-scope type specifies whether connections
|
1115
|
+
obtained through the given resource manager connection
|
1116
|
+
factory reference can be shared. The value, if specified,
|
1117
|
+
must be one of the two following:
|
1118
|
+
|
1119
|
+
Shareable
|
1120
|
+
Unshareable
|
1121
|
+
|
1122
|
+
The default value is Shareable.
|
1123
|
+
|
1124
|
+
</xsd:documentation>
|
1125
|
+
</xsd:annotation>
|
1126
|
+
<xsd:simpleContent>
|
1127
|
+
<xsd:restriction base="j2ee:string">
|
1128
|
+
<xsd:enumeration value="Shareable"/>
|
1129
|
+
<xsd:enumeration value="Unshareable"/>
|
1130
|
+
</xsd:restriction>
|
1131
|
+
</xsd:simpleContent>
|
1132
|
+
</xsd:complexType>
|
1133
|
+
|
1134
|
+
<!-- **************************************************** -->
|
1135
|
+
|
1136
|
+
<xsd:complexType name="resource-env-refType">
|
1137
|
+
<xsd:annotation>
|
1138
|
+
<xsd:documentation>
|
1139
|
+
<![CDATA[
|
1140
|
+
|
1141
|
+
The resource-env-refType is used to define
|
1142
|
+
resource-env-type elements. It contains a declaration of a
|
1143
|
+
Deployment Component's reference to an administered object
|
1144
|
+
associated with a resource in the Deployment Component's
|
1145
|
+
environment. It consists of an optional description, the
|
1146
|
+
resource environment reference name, and an indication of
|
1147
|
+
the resource environment reference type expected by the
|
1148
|
+
Deployment Component code.
|
1149
|
+
|
1150
|
+
Example:
|
1151
|
+
|
1152
|
+
<resource-env-ref>
|
1153
|
+
<resource-env-ref-name>jms/StockQueue
|
1154
|
+
</resource-env-ref-name>
|
1155
|
+
<resource-env-ref-type>javax.jms.Queue
|
1156
|
+
</resource-env-ref-type>
|
1157
|
+
</resource-env-ref>
|
1158
|
+
|
1159
|
+
]]>
|
1160
|
+
</xsd:documentation>
|
1161
|
+
</xsd:annotation>
|
1162
|
+
|
1163
|
+
<xsd:sequence>
|
1164
|
+
<xsd:element name="description"
|
1165
|
+
type="j2ee:descriptionType"
|
1166
|
+
minOccurs="0"
|
1167
|
+
maxOccurs="unbounded"/>
|
1168
|
+
<xsd:element name="resource-env-ref-name"
|
1169
|
+
type="j2ee:jndi-nameType">
|
1170
|
+
<xsd:annotation>
|
1171
|
+
<xsd:documentation>
|
1172
|
+
|
1173
|
+
The resource-env-ref-name element specifies the name
|
1174
|
+
of a resource environment reference; its value is
|
1175
|
+
the environment entry name used in
|
1176
|
+
the Deployment Component code. The name is a JNDI
|
1177
|
+
name relative to the java:comp/env context and must
|
1178
|
+
be unique within a Deployment Component.
|
1179
|
+
|
1180
|
+
</xsd:documentation>
|
1181
|
+
</xsd:annotation>
|
1182
|
+
</xsd:element>
|
1183
|
+
|
1184
|
+
<xsd:element name="resource-env-ref-type"
|
1185
|
+
type="j2ee:fully-qualified-classType">
|
1186
|
+
<xsd:annotation>
|
1187
|
+
<xsd:documentation>
|
1188
|
+
|
1189
|
+
The resource-env-ref-type element specifies the type
|
1190
|
+
of a resource environment reference. It is the
|
1191
|
+
fully qualified name of a Java language class or
|
1192
|
+
interface.
|
1193
|
+
|
1194
|
+
</xsd:documentation>
|
1195
|
+
</xsd:annotation>
|
1196
|
+
</xsd:element>
|
1197
|
+
|
1198
|
+
</xsd:sequence>
|
1199
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
1200
|
+
</xsd:complexType>
|
1201
|
+
|
1202
|
+
<!-- **************************************************** -->
|
1203
|
+
|
1204
|
+
<xsd:complexType name="resource-refType">
|
1205
|
+
<xsd:annotation>
|
1206
|
+
<xsd:documentation>
|
1207
|
+
<![CDATA[
|
1208
|
+
|
1209
|
+
The resource-refType contains a declaration of a
|
1210
|
+
Deployment Component's reference to an external resource. It
|
1211
|
+
consists of an optional description, the resource manager
|
1212
|
+
connection factory reference name, the indication of the
|
1213
|
+
resource manager connection factory type expected by the
|
1214
|
+
Deployment Component code, the type of authentication
|
1215
|
+
(Application or Container), and an optional specification of
|
1216
|
+
the shareability of connections obtained from the resource
|
1217
|
+
(Shareable or Unshareable).
|
1218
|
+
|
1219
|
+
Example:
|
1220
|
+
|
1221
|
+
<resource-ref>
|
1222
|
+
<res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
|
1223
|
+
<res-type>javax.sql.DataSource</res-type>
|
1224
|
+
<res-auth>Container</res-auth>
|
1225
|
+
<res-sharing-scope>Shareable</res-sharing-scope>
|
1226
|
+
</resource-ref>
|
1227
|
+
|
1228
|
+
]]>
|
1229
|
+
</xsd:documentation>
|
1230
|
+
</xsd:annotation>
|
1231
|
+
|
1232
|
+
<xsd:sequence>
|
1233
|
+
<xsd:element name="description"
|
1234
|
+
type="j2ee:descriptionType"
|
1235
|
+
minOccurs="0"
|
1236
|
+
maxOccurs="unbounded"/>
|
1237
|
+
<xsd:element name="res-ref-name"
|
1238
|
+
type="j2ee:jndi-nameType">
|
1239
|
+
<xsd:annotation>
|
1240
|
+
<xsd:documentation>
|
1241
|
+
|
1242
|
+
The res-ref-name element specifies the name of a
|
1243
|
+
resource manager connection factory reference.
|
1244
|
+
The name is a JNDI name relative to the
|
1245
|
+
java:comp/env context.
|
1246
|
+
The name must be unique within a Deployment File.
|
1247
|
+
|
1248
|
+
</xsd:documentation>
|
1249
|
+
</xsd:annotation>
|
1250
|
+
</xsd:element>
|
1251
|
+
|
1252
|
+
<xsd:element name="res-type"
|
1253
|
+
type="j2ee:fully-qualified-classType">
|
1254
|
+
<xsd:annotation>
|
1255
|
+
<xsd:documentation>
|
1256
|
+
|
1257
|
+
The res-type element specifies the type of the data
|
1258
|
+
source. The type is specified by the fully qualified
|
1259
|
+
Java language class or interface
|
1260
|
+
expected to be implemented by the data source.
|
1261
|
+
|
1262
|
+
</xsd:documentation>
|
1263
|
+
</xsd:annotation>
|
1264
|
+
</xsd:element>
|
1265
|
+
|
1266
|
+
<xsd:element name="res-auth"
|
1267
|
+
type="j2ee:res-authType"/>
|
1268
|
+
|
1269
|
+
<xsd:element name="res-sharing-scope"
|
1270
|
+
type="j2ee:res-sharing-scopeType"
|
1271
|
+
minOccurs="0"/>
|
1272
|
+
</xsd:sequence>
|
1273
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
1274
|
+
</xsd:complexType>
|
1275
|
+
|
1276
|
+
<!-- **************************************************** -->
|
1277
|
+
|
1278
|
+
<xsd:complexType name="role-nameType">
|
1279
|
+
<xsd:annotation>
|
1280
|
+
<xsd:documentation>
|
1281
|
+
|
1282
|
+
The role-nameType designates the name of a security role.
|
1283
|
+
|
1284
|
+
The name must conform to the lexical rules for a token.
|
1285
|
+
|
1286
|
+
</xsd:documentation>
|
1287
|
+
</xsd:annotation>
|
1288
|
+
|
1289
|
+
<xsd:simpleContent>
|
1290
|
+
<xsd:restriction base="j2ee:string"/>
|
1291
|
+
</xsd:simpleContent>
|
1292
|
+
</xsd:complexType>
|
1293
|
+
|
1294
|
+
<!-- **************************************************** -->
|
1295
|
+
|
1296
|
+
<xsd:complexType name="run-asType">
|
1297
|
+
<xsd:annotation>
|
1298
|
+
<xsd:documentation>
|
1299
|
+
|
1300
|
+
The run-asType specifies the run-as identity to be
|
1301
|
+
used for the execution of a component. It contains an
|
1302
|
+
optional description, and the name of a security role.
|
1303
|
+
|
1304
|
+
</xsd:documentation>
|
1305
|
+
</xsd:annotation>
|
1306
|
+
|
1307
|
+
<xsd:sequence>
|
1308
|
+
<xsd:element name="description"
|
1309
|
+
type="j2ee:descriptionType"
|
1310
|
+
minOccurs="0"
|
1311
|
+
maxOccurs="unbounded"/>
|
1312
|
+
<xsd:element name="role-name"
|
1313
|
+
type="j2ee:role-nameType"/>
|
1314
|
+
</xsd:sequence>
|
1315
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
1316
|
+
</xsd:complexType>
|
1317
|
+
|
1318
|
+
<!-- **************************************************** -->
|
1319
|
+
|
1320
|
+
<xsd:complexType name="security-role-refType">
|
1321
|
+
<xsd:annotation>
|
1322
|
+
<xsd:documentation>
|
1323
|
+
|
1324
|
+
The security-role-refType contains the declaration of a
|
1325
|
+
security role reference in a component's or a
|
1326
|
+
Deployment Component's code. The declaration consists of an
|
1327
|
+
optional description, the security role name used in the
|
1328
|
+
code, and an optional link to a security role. If the
|
1329
|
+
security role is not specified, the Deployer must choose an
|
1330
|
+
appropriate security role.
|
1331
|
+
|
1332
|
+
</xsd:documentation>
|
1333
|
+
</xsd:annotation>
|
1334
|
+
|
1335
|
+
<xsd:sequence>
|
1336
|
+
<xsd:element name="description"
|
1337
|
+
type="j2ee:descriptionType"
|
1338
|
+
minOccurs="0"
|
1339
|
+
maxOccurs="unbounded"/>
|
1340
|
+
<xsd:element name="role-name"
|
1341
|
+
type="j2ee:role-nameType">
|
1342
|
+
<xsd:annotation>
|
1343
|
+
<xsd:documentation>
|
1344
|
+
|
1345
|
+
The value of the role-name element must be the String used
|
1346
|
+
as the parameter to the
|
1347
|
+
EJBContext.isCallerInRole(String roleName) method or the
|
1348
|
+
HttpServletRequest.isUserInRole(String role) method.
|
1349
|
+
|
1350
|
+
</xsd:documentation>
|
1351
|
+
</xsd:annotation>
|
1352
|
+
</xsd:element>
|
1353
|
+
|
1354
|
+
<xsd:element name="role-link"
|
1355
|
+
type="j2ee:role-nameType"
|
1356
|
+
minOccurs="0">
|
1357
|
+
<xsd:annotation>
|
1358
|
+
<xsd:documentation>
|
1359
|
+
|
1360
|
+
The role-link element is a reference to a defined
|
1361
|
+
security role. The role-link element must contain
|
1362
|
+
the name of one of the security roles defined in the
|
1363
|
+
security-role elements.
|
1364
|
+
|
1365
|
+
</xsd:documentation>
|
1366
|
+
</xsd:annotation>
|
1367
|
+
</xsd:element>
|
1368
|
+
</xsd:sequence>
|
1369
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
1370
|
+
</xsd:complexType>
|
1371
|
+
|
1372
|
+
<!-- **************************************************** -->
|
1373
|
+
|
1374
|
+
<xsd:complexType name="security-roleType">
|
1375
|
+
<xsd:annotation>
|
1376
|
+
<xsd:documentation>
|
1377
|
+
<![CDATA[
|
1378
|
+
|
1379
|
+
The security-roleType contains the definition of a security
|
1380
|
+
role. The definition consists of an optional description of the
|
1381
|
+
security role, and the security role name.
|
1382
|
+
|
1383
|
+
Example:
|
1384
|
+
|
1385
|
+
<security-role>
|
1386
|
+
<description>
|
1387
|
+
This role includes all employees who are authorized
|
1388
|
+
to access the employee service application.
|
1389
|
+
</description>
|
1390
|
+
<role-name>employee</role-name>
|
1391
|
+
</security-role>
|
1392
|
+
|
1393
|
+
]]>
|
1394
|
+
</xsd:documentation>
|
1395
|
+
</xsd:annotation>
|
1396
|
+
|
1397
|
+
<xsd:sequence>
|
1398
|
+
<xsd:element name="description"
|
1399
|
+
type="j2ee:descriptionType"
|
1400
|
+
minOccurs="0"
|
1401
|
+
maxOccurs="unbounded"/>
|
1402
|
+
<xsd:element name="role-name"
|
1403
|
+
type="j2ee:role-nameType"/>
|
1404
|
+
</xsd:sequence>
|
1405
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
1406
|
+
</xsd:complexType>
|
1407
|
+
|
1408
|
+
<!-- **************************************************** -->
|
1409
|
+
|
1410
|
+
<xsd:complexType name="string">
|
1411
|
+
<xsd:annotation>
|
1412
|
+
<xsd:documentation>
|
1413
|
+
|
1414
|
+
This is a special string datatype that is defined by J2EE as
|
1415
|
+
a base type for defining collapsed strings. When schemas
|
1416
|
+
require trailing/leading space elimination as well as
|
1417
|
+
collapsing the existing whitespace, this base type may be
|
1418
|
+
used.
|
1419
|
+
|
1420
|
+
</xsd:documentation>
|
1421
|
+
</xsd:annotation>
|
1422
|
+
<xsd:simpleContent>
|
1423
|
+
<xsd:extension base="xsd:token">
|
1424
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
1425
|
+
</xsd:extension>
|
1426
|
+
</xsd:simpleContent>
|
1427
|
+
</xsd:complexType>
|
1428
|
+
|
1429
|
+
<!-- **************************************************** -->
|
1430
|
+
|
1431
|
+
<xsd:complexType name="true-falseType">
|
1432
|
+
<xsd:annotation>
|
1433
|
+
<xsd:documentation>
|
1434
|
+
|
1435
|
+
This simple type designates a boolean with only two
|
1436
|
+
permissible values
|
1437
|
+
|
1438
|
+
- true
|
1439
|
+
- false
|
1440
|
+
|
1441
|
+
</xsd:documentation>
|
1442
|
+
</xsd:annotation>
|
1443
|
+
<xsd:simpleContent>
|
1444
|
+
<xsd:restriction base="j2ee:xsdBooleanType">
|
1445
|
+
<xsd:pattern value="(true|false)"/>
|
1446
|
+
</xsd:restriction>
|
1447
|
+
</xsd:simpleContent>
|
1448
|
+
</xsd:complexType>
|
1449
|
+
|
1450
|
+
<!-- **************************************************** -->
|
1451
|
+
|
1452
|
+
<xsd:complexType name="url-patternType">
|
1453
|
+
<xsd:annotation>
|
1454
|
+
<xsd:documentation>
|
1455
|
+
|
1456
|
+
The url-patternType contains the url pattern of the mapping.
|
1457
|
+
It must follow the rules specified in Section 11.2 of the
|
1458
|
+
Servlet API Specification. This pattern is assumed to be in
|
1459
|
+
URL-decoded form and must not contain CR(#xD) or LF(#xA).
|
1460
|
+
If it contains those characters, the container must inform
|
1461
|
+
the developer with a descriptive error message.
|
1462
|
+
The container must preserve all characters including whitespaces.
|
1463
|
+
|
1464
|
+
</xsd:documentation>
|
1465
|
+
</xsd:annotation>
|
1466
|
+
<xsd:simpleContent>
|
1467
|
+
<xsd:extension base="xsd:string"/>
|
1468
|
+
</xsd:simpleContent>
|
1469
|
+
</xsd:complexType>
|
1470
|
+
|
1471
|
+
<!-- **************************************************** -->
|
1472
|
+
|
1473
|
+
<xsd:complexType name="xsdAnyURIType">
|
1474
|
+
<xsd:annotation>
|
1475
|
+
<xsd:documentation>
|
1476
|
+
|
1477
|
+
This type adds an "id" attribute to xsd:anyURI.
|
1478
|
+
|
1479
|
+
</xsd:documentation>
|
1480
|
+
</xsd:annotation>
|
1481
|
+
<xsd:simpleContent>
|
1482
|
+
<xsd:extension base="xsd:anyURI">
|
1483
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
1484
|
+
</xsd:extension>
|
1485
|
+
</xsd:simpleContent>
|
1486
|
+
</xsd:complexType>
|
1487
|
+
|
1488
|
+
<!-- **************************************************** -->
|
1489
|
+
|
1490
|
+
<xsd:complexType name="xsdBooleanType">
|
1491
|
+
<xsd:annotation>
|
1492
|
+
<xsd:documentation>
|
1493
|
+
|
1494
|
+
This type adds an "id" attribute to xsd:boolean.
|
1495
|
+
|
1496
|
+
</xsd:documentation>
|
1497
|
+
</xsd:annotation>
|
1498
|
+
<xsd:simpleContent>
|
1499
|
+
<xsd:extension base="xsd:boolean">
|
1500
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
1501
|
+
</xsd:extension>
|
1502
|
+
</xsd:simpleContent>
|
1503
|
+
</xsd:complexType>
|
1504
|
+
|
1505
|
+
<!-- **************************************************** -->
|
1506
|
+
|
1507
|
+
<xsd:complexType name="xsdIntegerType">
|
1508
|
+
<xsd:annotation>
|
1509
|
+
<xsd:documentation>
|
1510
|
+
|
1511
|
+
This type adds an "id" attribute to xsd:integer.
|
1512
|
+
|
1513
|
+
</xsd:documentation>
|
1514
|
+
</xsd:annotation>
|
1515
|
+
<xsd:simpleContent>
|
1516
|
+
<xsd:extension base="xsd:integer">
|
1517
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
1518
|
+
</xsd:extension>
|
1519
|
+
</xsd:simpleContent>
|
1520
|
+
</xsd:complexType>
|
1521
|
+
|
1522
|
+
<!-- **************************************************** -->
|
1523
|
+
|
1524
|
+
<xsd:complexType name="xsdNMTOKENType">
|
1525
|
+
<xsd:annotation>
|
1526
|
+
<xsd:documentation>
|
1527
|
+
|
1528
|
+
This type adds an "id" attribute to xsd:NMTOKEN.
|
1529
|
+
|
1530
|
+
</xsd:documentation>
|
1531
|
+
</xsd:annotation>
|
1532
|
+
<xsd:simpleContent>
|
1533
|
+
<xsd:extension base="xsd:NMTOKEN">
|
1534
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
1535
|
+
</xsd:extension>
|
1536
|
+
</xsd:simpleContent>
|
1537
|
+
</xsd:complexType>
|
1538
|
+
|
1539
|
+
<!-- **************************************************** -->
|
1540
|
+
|
1541
|
+
<xsd:complexType name="xsdNonNegativeIntegerType">
|
1542
|
+
<xsd:annotation>
|
1543
|
+
<xsd:documentation>
|
1544
|
+
|
1545
|
+
This type adds an "id" attribute to xsd:nonNegativeInteger.
|
1546
|
+
|
1547
|
+
</xsd:documentation>
|
1548
|
+
</xsd:annotation>
|
1549
|
+
<xsd:simpleContent>
|
1550
|
+
<xsd:extension base="xsd:nonNegativeInteger">
|
1551
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
1552
|
+
</xsd:extension>
|
1553
|
+
</xsd:simpleContent>
|
1554
|
+
</xsd:complexType>
|
1555
|
+
|
1556
|
+
<!-- **************************************************** -->
|
1557
|
+
|
1558
|
+
<xsd:complexType name="xsdPositiveIntegerType">
|
1559
|
+
<xsd:annotation>
|
1560
|
+
<xsd:documentation>
|
1561
|
+
|
1562
|
+
This type adds an "id" attribute to xsd:positiveInteger.
|
1563
|
+
|
1564
|
+
</xsd:documentation>
|
1565
|
+
</xsd:annotation>
|
1566
|
+
<xsd:simpleContent>
|
1567
|
+
<xsd:extension base="xsd:positiveInteger">
|
1568
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
1569
|
+
</xsd:extension>
|
1570
|
+
</xsd:simpleContent>
|
1571
|
+
</xsd:complexType>
|
1572
|
+
|
1573
|
+
<!-- **************************************************** -->
|
1574
|
+
|
1575
|
+
<xsd:complexType name="xsdQNameType">
|
1576
|
+
<xsd:annotation>
|
1577
|
+
<xsd:documentation>
|
1578
|
+
|
1579
|
+
This type adds an "id" attribute to xsd:QName.
|
1580
|
+
|
1581
|
+
</xsd:documentation>
|
1582
|
+
</xsd:annotation>
|
1583
|
+
<xsd:simpleContent>
|
1584
|
+
<xsd:extension base="xsd:QName">
|
1585
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
1586
|
+
</xsd:extension>
|
1587
|
+
</xsd:simpleContent>
|
1588
|
+
</xsd:complexType>
|
1589
|
+
|
1590
|
+
<!-- **************************************************** -->
|
1591
|
+
|
1592
|
+
<xsd:complexType name="xsdStringType">
|
1593
|
+
<xsd:annotation>
|
1594
|
+
<xsd:documentation>
|
1595
|
+
|
1596
|
+
This type adds an "id" attribute to xsd:string.
|
1597
|
+
|
1598
|
+
</xsd:documentation>
|
1599
|
+
</xsd:annotation>
|
1600
|
+
<xsd:simpleContent>
|
1601
|
+
<xsd:extension base="xsd:string">
|
1602
|
+
<xsd:attribute name="id" type="xsd:ID"/>
|
1603
|
+
</xsd:extension>
|
1604
|
+
</xsd:simpleContent>
|
1605
|
+
</xsd:complexType>
|
1606
|
+
|
1607
|
+
</xsd:schema>
|
1608
|
+
|