glassfish 0.1.1-universal-java-1.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
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,345 @@
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="1.1">
10
+ <xsd:annotation>
11
+ <xsd:documentation>
12
+ @(#)j2ee_web_services_client_1_1.xsds 1.10 02/11/03
13
+ </xsd:documentation>
14
+ </xsd:annotation>
15
+
16
+ <xsd:annotation>
17
+ <xsd:documentation>
18
+
19
+ Copyright 2003 Sun Microsystems, Inc., 901 San Antonio
20
+ Road, Palo Alto, California 94303, U.S.A. All rights
21
+ reserved.
22
+
23
+ Sun Microsystems, Inc. has intellectual property rights
24
+ relating to technology described in this document. In
25
+ particular, and without limitation, these intellectual
26
+ property rights may include one or more of the U.S. patents
27
+ listed at http://www.sun.com/patents and one or more
28
+ additional patents or pending patent applications in the
29
+ U.S. and other countries.
30
+
31
+ This document and the technology which it describes are
32
+ distributed under licenses restricting their use, copying,
33
+ distribution, and decompilation. No part of this document
34
+ may be reproduced in any form by any means without prior
35
+ written authorization of Sun and its licensors, if any.
36
+
37
+ Third-party software, including font technology, is
38
+ copyrighted and licensed from Sun suppliers.
39
+
40
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
41
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
42
+ Cup logo are trademarks or registered trademarks of Sun
43
+ Microsystems, Inc. in the U.S. and other countries.
44
+
45
+ Federal Acquisitions: Commercial Software - Government Users
46
+ Subject to Standard License Terms and Conditions.
47
+
48
+ </xsd:documentation>
49
+ </xsd:annotation>
50
+
51
+ <xsd:annotation>
52
+ <xsd:documentation>
53
+
54
+ (C) Copyright International Business Machines Corporation 2002
55
+
56
+ </xsd:documentation>
57
+ </xsd:annotation>
58
+
59
+
60
+ <!-- **************************************************** -->
61
+
62
+ <xsd:complexType name="port-component-refType">
63
+ <xsd:annotation>
64
+ <xsd:documentation>
65
+
66
+ The port-component-ref element declares a client dependency
67
+ on the container for resolving a Service Endpoint Interface
68
+ to a WSDL port. It optionally associates the Service Endpoint
69
+ Interface with a particular port-component. This is only used
70
+ by the container for a Service.getPort(Class) method call.
71
+
72
+ </xsd:documentation>
73
+ </xsd:annotation>
74
+
75
+ <xsd:sequence>
76
+ <xsd:element name="service-endpoint-interface"
77
+ type="j2ee:fully-qualified-classType">
78
+ <xsd:annotation>
79
+ <xsd:documentation>
80
+
81
+ The service-endpoint-interface element defines a fully qualified
82
+ Java class that represents the Service Endpoint Interface of a
83
+ WSDL port.
84
+
85
+ </xsd:documentation>
86
+ </xsd:annotation>
87
+ </xsd:element>
88
+
89
+ <xsd:element name="port-component-link"
90
+ type="j2ee:string"
91
+ minOccurs="0" maxOccurs="1">
92
+ <xsd:annotation>
93
+ <xsd:documentation>
94
+
95
+ The port-component-link element links a port-component-ref
96
+ to a specific port-component required to be made available
97
+ by a service reference.
98
+
99
+ The value of a port-component-link must be the
100
+ port-component-name of a port-component in the same module
101
+ or another module in the same application unit. The syntax
102
+ for specification follows the syntax defined for ejb-link
103
+ in the EJB 2.0 specification.
104
+
105
+ </xsd:documentation>
106
+ </xsd:annotation>
107
+ </xsd:element>
108
+ </xsd:sequence>
109
+ <xsd:attribute name="id" type="xsd:ID"/>
110
+ </xsd:complexType>
111
+
112
+ <!-- **************************************************** -->
113
+
114
+ <xsd:group name="service-refGroup">
115
+ <xsd:sequence>
116
+ <xsd:element name="service-ref"
117
+ type="j2ee:service-refType"
118
+ minOccurs="0" maxOccurs="unbounded">
119
+ <xsd:key name="service-ref_handler-name-key">
120
+ <xsd:annotation>
121
+ <xsd:documentation>
122
+
123
+ Defines the name of the handler. The name must be unique
124
+ within the module.
125
+
126
+ </xsd:documentation>
127
+ </xsd:annotation>
128
+ <xsd:selector xpath="j2ee:handler"/>
129
+ <xsd:field xpath="j2ee:handler-name"/>
130
+ </xsd:key>
131
+ </xsd:element>
132
+ </xsd:sequence>
133
+ </xsd:group>
134
+
135
+ <!-- **************************************************** -->
136
+
137
+ <xsd:complexType name="service-refType">
138
+ <xsd:annotation>
139
+ <xsd:documentation>
140
+
141
+ The service-ref element declares a reference to a Web
142
+ service. It contains optional description, display name and
143
+ icons, a declaration of the required Service interface,
144
+ an optional WSDL document location, an optional set
145
+ of JAX-RPC mappings, an optional QName for the service element,
146
+ an optional set of Service Endpoint Interfaces to be resolved
147
+ by the container to a WSDL port, and an optional set of handlers.
148
+
149
+ </xsd:documentation>
150
+ </xsd:annotation>
151
+
152
+ <xsd:sequence>
153
+ <xsd:group ref="j2ee:descriptionGroup"/>
154
+ <xsd:element name="service-ref-name"
155
+ type="j2ee:jndi-nameType">
156
+ <xsd:annotation>
157
+ <xsd:documentation>
158
+
159
+ The service-ref-name element declares logical name that the
160
+ components in the module use to look up the Web service. It
161
+ is recommended that all service reference names start with
162
+ "service/".
163
+
164
+ </xsd:documentation>
165
+ </xsd:annotation>
166
+ </xsd:element>
167
+
168
+ <xsd:element name="service-interface"
169
+ type="j2ee:fully-qualified-classType">
170
+ <xsd:annotation>
171
+ <xsd:documentation>
172
+
173
+ The service-interface element declares the fully qualified class
174
+ name of the JAX-RPC Service interface the client depends on.
175
+ In most cases the value will be javax.xml.rpc.Service. A JAX-RPC
176
+ generated Service Interface class may also be specified.
177
+
178
+ </xsd:documentation>
179
+ </xsd:annotation>
180
+ </xsd:element>
181
+
182
+ <xsd:element name="wsdl-file"
183
+ type="j2ee:xsdAnyURIType"
184
+ minOccurs="0" maxOccurs="1">
185
+ <xsd:annotation>
186
+ <xsd:documentation>
187
+
188
+ The wsdl-file element contains the URI location of a WSDL
189
+ file. The location is relative to the root of the module.
190
+
191
+ </xsd:documentation>
192
+ </xsd:annotation>
193
+ </xsd:element>
194
+
195
+ <xsd:element name="jaxrpc-mapping-file"
196
+ type="j2ee:pathType"
197
+ minOccurs="0" maxOccurs="1">
198
+ <xsd:annotation>
199
+ <xsd:documentation>
200
+
201
+ The jaxrpc-mapping-file element contains the name of a file that
202
+ describes the JAX-RPC mapping between the Java interaces used by
203
+ the application and the WSDL description in the wsdl-file. The
204
+ file name is a relative path within the module file.
205
+
206
+ </xsd:documentation>
207
+ </xsd:annotation>
208
+ </xsd:element>
209
+
210
+ <xsd:element name="service-qname"
211
+ type="j2ee:xsdQNameType"
212
+ minOccurs="0" maxOccurs="1">
213
+ <xsd:annotation>
214
+ <xsd:documentation>
215
+
216
+ The service-qname element declares the specific WSDL service
217
+ element that is being refered to. It is not specified if no
218
+ wsdl-file is declared.
219
+
220
+ </xsd:documentation>
221
+ </xsd:annotation>
222
+ </xsd:element>
223
+
224
+ <xsd:element name="port-component-ref"
225
+ type="j2ee:port-component-refType"
226
+ minOccurs="0" maxOccurs="unbounded">
227
+ <xsd:annotation>
228
+ <xsd:documentation>
229
+
230
+ The port-component-ref element declares a client dependency
231
+ on the container for resolving a Service Endpoint Interface
232
+ to a WSDL port. It optionally associates the Service Endpoint
233
+ Interface with a particular port-component. This is only used
234
+ by the container for a Service.getPort(Class) method call.
235
+
236
+ </xsd:documentation>
237
+ </xsd:annotation>
238
+ </xsd:element>
239
+
240
+ <xsd:element name="handler"
241
+ type="j2ee:service-ref_handlerType"
242
+ minOccurs="0" maxOccurs="unbounded">
243
+ <xsd:annotation>
244
+ <xsd:documentation>
245
+
246
+ Declares the handler for a port-component. Handlers can
247
+ access the init-param name/value pairs using the
248
+ HandlerInfo interface. If port-name is not specified, the
249
+ handler is assumed to be associated with all ports of the
250
+ service.
251
+
252
+ </xsd:documentation>
253
+ </xsd:annotation>
254
+ </xsd:element>
255
+ </xsd:sequence>
256
+ <xsd:attribute name="id" type="xsd:ID"/>
257
+ </xsd:complexType>
258
+
259
+ <!-- **************************************************** -->
260
+
261
+ <xsd:complexType name="service-ref_handlerType">
262
+ <xsd:annotation>
263
+ <xsd:documentation>
264
+
265
+ Declares the handler for a port-component. Handlers can access the
266
+ init-param name/value pairs using the HandlerInfo interface. If
267
+ port-name is not specified, the handler is assumed to be associated
268
+ with all ports of the service.
269
+
270
+ Used in: service-ref
271
+
272
+ </xsd:documentation>
273
+ </xsd:annotation>
274
+ <xsd:sequence>
275
+ <xsd:group ref="j2ee:descriptionGroup"/>
276
+ <xsd:element name="handler-name"
277
+ type="j2ee:string">
278
+ <xsd:annotation>
279
+ <xsd:documentation>
280
+
281
+ Defines the name of the handler. The name must be unique
282
+ within the module.
283
+
284
+ </xsd:documentation>
285
+ </xsd:annotation>
286
+ </xsd:element>
287
+ <xsd:element name="handler-class"
288
+ type="j2ee:fully-qualified-classType">
289
+ <xsd:annotation>
290
+ <xsd:documentation>
291
+
292
+ Defines a fully qualified class name for the handler
293
+ implementation.
294
+
295
+ </xsd:documentation>
296
+ </xsd:annotation>
297
+ </xsd:element>
298
+ <xsd:element name="init-param"
299
+ type="j2ee:param-valueType"
300
+ minOccurs="0" maxOccurs="unbounded"/>
301
+
302
+ <xsd:element name="soap-header"
303
+ type="j2ee:xsdQNameType"
304
+ minOccurs="0" maxOccurs="unbounded">
305
+ <xsd:annotation>
306
+ <xsd:documentation>
307
+
308
+ Defines the QName of a SOAP header that will be processed
309
+ by the handler.
310
+
311
+ </xsd:documentation>
312
+ </xsd:annotation>
313
+ </xsd:element>
314
+
315
+ <xsd:element name="soap-role"
316
+ type="j2ee:string"
317
+ minOccurs="0" maxOccurs="unbounded">
318
+ <xsd:annotation>
319
+ <xsd:documentation>
320
+
321
+ The soap-role element contains a SOAP actor definition that
322
+ the Handler will play as a role.
323
+
324
+ </xsd:documentation>
325
+ </xsd:annotation>
326
+ </xsd:element>
327
+
328
+ <xsd:element name="port-name"
329
+ type="j2ee:string"
330
+ minOccurs="0" maxOccurs="unbounded">
331
+ <xsd:annotation>
332
+ <xsd:documentation>
333
+
334
+ The port-name element defines the WSDL port-name that a
335
+ handler should be associated with.
336
+
337
+ </xsd:documentation>
338
+ </xsd:annotation>
339
+ </xsd:element>
340
+ </xsd:sequence>
341
+ <xsd:attribute name="id" type="xsd:ID"/>
342
+ </xsd:complexType>
343
+
344
+ </xsd:schema>
345
+
@@ -0,0 +1,2096 @@
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+
3
+ <xsd:schema
4
+ targetNamespace="http://java.sun.com/xml/ns/javaee"
5
+ xmlns:javaee="http://java.sun.com/xml/ns/javaee"
6
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
7
+ elementFormDefault="qualified"
8
+ attributeFormDefault="unqualified"
9
+ version="5">
10
+ <xsd:annotation>
11
+ <xsd:documentation>
12
+ @(#)javaee_5.xsds 1.65 06/02/17
13
+ </xsd:documentation>
14
+ </xsd:annotation>
15
+
16
+ <xsd:annotation>
17
+ <xsd:documentation>
18
+
19
+ Copyright 2003-2005 Sun Microsystems, Inc.
20
+ 4150 Network Circle
21
+ Santa Clara, California 95054
22
+ U.S.A
23
+ All rights reserved.
24
+
25
+ Sun Microsystems, Inc. has intellectual property rights
26
+ relating to technology described in this document. In
27
+ particular, and without limitation, these intellectual
28
+ property rights may include one or more of the U.S. patents
29
+ listed at http://www.sun.com/patents and one or more
30
+ additional patents or pending patent applications in the
31
+ U.S. and other countries.
32
+
33
+ This document and the technology which it describes are
34
+ distributed under licenses restricting their use, copying,
35
+ distribution, and decompilation. No part of this document
36
+ may be reproduced in any form by any means without prior
37
+ written authorization of Sun and its licensors, if any.
38
+
39
+ Third-party software, including font technology, is
40
+ copyrighted and licensed from Sun suppliers.
41
+
42
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
43
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
44
+ Cup logo are trademarks or registered trademarks of Sun
45
+ Microsystems, Inc. in the U.S. and other countries.
46
+
47
+ Federal Acquisitions: Commercial Software - Government Users
48
+ Subject to Standard License Terms and Conditions.
49
+
50
+ </xsd:documentation>
51
+ </xsd:annotation>
52
+
53
+ <xsd:annotation>
54
+ <xsd:documentation>
55
+
56
+ The following definitions that appear in the common
57
+ shareable schema(s) of J2EE deployment descriptors should be
58
+ interpreted with respect to the context they are included:
59
+
60
+ Deployment Component may indicate one of the following:
61
+ j2ee application;
62
+ application client;
63
+ web application;
64
+ enterprise bean;
65
+ resource adapter;
66
+
67
+ Deployment File may indicate one of the following:
68
+ ear file;
69
+ war file;
70
+ jar file;
71
+ rar file;
72
+
73
+ </xsd:documentation>
74
+ </xsd:annotation>
75
+
76
+ <xsd:import namespace="http://www.w3.org/XML/1998/namespace"
77
+ schemaLocation="http://www.w3.org/2001/xml.xsd"/>
78
+
79
+ <xsd:include schemaLocation="javaee_web_services_client_1_2.xsd"/>
80
+
81
+
82
+ <!-- **************************************************** -->
83
+
84
+ <xsd:group name="descriptionGroup">
85
+ <xsd:annotation>
86
+ <xsd:documentation>
87
+
88
+ This group keeps the usage of the contained description related
89
+ elements consistent across Java EE deployment descriptors.
90
+
91
+ All elements may occur multiple times with different languages,
92
+ to support localization of the content.
93
+
94
+ </xsd:documentation>
95
+ </xsd:annotation>
96
+ <xsd:sequence>
97
+ <xsd:element name="description"
98
+ type="javaee:descriptionType"
99
+ minOccurs="0"
100
+ maxOccurs="unbounded"/>
101
+ <xsd:element name="display-name"
102
+ type="javaee:display-nameType"
103
+ minOccurs="0"
104
+ maxOccurs="unbounded"/>
105
+ <xsd:element name="icon"
106
+ type="javaee:iconType"
107
+ minOccurs="0"
108
+ maxOccurs="unbounded"/>
109
+ </xsd:sequence>
110
+ </xsd:group>
111
+
112
+ <!-- **************************************************** -->
113
+
114
+ <xsd:complexType name="descriptionType">
115
+ <xsd:annotation>
116
+ <xsd:documentation>
117
+
118
+ The description type is used by a description element to
119
+ provide text describing the parent element. The elements
120
+ that use this type should include any information that the
121
+ Deployment Component's Deployment File file producer wants
122
+ to provide to the consumer of the Deployment Component's
123
+ Deployment File (i.e., to the Deployer). Typically, the
124
+ tools used by such a Deployment File consumer will display
125
+ the description when processing the parent element that
126
+ contains the description.
127
+
128
+ The lang attribute defines the language that the
129
+ description is provided in. The default value is "en" (English).
130
+
131
+ </xsd:documentation>
132
+ </xsd:annotation>
133
+ <xsd:simpleContent>
134
+ <xsd:extension base="javaee:xsdStringType">
135
+ <xsd:attribute ref="xml:lang"/>
136
+ </xsd:extension>
137
+ </xsd:simpleContent>
138
+ </xsd:complexType>
139
+
140
+ <!-- **************************************************** -->
141
+
142
+ <xsd:simpleType name="dewey-versionType">
143
+ <xsd:annotation>
144
+ <xsd:documentation>
145
+
146
+ This type defines a dewey decimal that is used
147
+ to describe versions of documents.
148
+
149
+ </xsd:documentation>
150
+ </xsd:annotation>
151
+
152
+ <xsd:restriction base="xsd:token">
153
+ <xsd:pattern value="\.?[0-9]+(\.[0-9]+)*"/>
154
+ </xsd:restriction>
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">
172
+ Employee Self Service
173
+ </display-name>
174
+
175
+ The value of the xml:lang attribute is "en" (English) by default.
176
+
177
+ ]]>
178
+ </xsd:documentation>
179
+ </xsd:annotation>
180
+ <xsd:simpleContent>
181
+ <xsd:extension base="javaee:string">
182
+ <xsd:attribute ref="xml:lang"/>
183
+ </xsd:extension>
184
+ </xsd:simpleContent>
185
+ </xsd:complexType>
186
+
187
+ <!-- **************************************************** -->
188
+
189
+ <xsd:complexType name="ejb-linkType">
190
+ <xsd:annotation>
191
+ <xsd:documentation>
192
+ <![CDATA[
193
+
194
+ The ejb-linkType is used by ejb-link
195
+ elements in the ejb-ref or ejb-local-ref elements to specify
196
+ that an EJB reference is linked to enterprise bean.
197
+
198
+ The value of the ejb-link element must be the ejb-name of an
199
+ enterprise bean in the same ejb-jar file or in another ejb-jar
200
+ file in the same Java EE application unit.
201
+
202
+ Alternatively, the name in the ejb-link element may be
203
+ composed of a path name specifying the ejb-jar containing the
204
+ referenced enterprise bean with the ejb-name of the target
205
+ bean appended and separated from the path name by "#". The
206
+ path name is relative to the Deployment File containing
207
+ Deployment Component that is referencing the enterprise
208
+ bean. This allows multiple enterprise beans with the same
209
+ ejb-name to be uniquely identified.
210
+
211
+ Examples:
212
+
213
+ <ejb-link>EmployeeRecord</ejb-link>
214
+
215
+ <ejb-link>../products/product.jar#ProductEJB</ejb-link>
216
+
217
+ ]]>
218
+ </xsd:documentation>
219
+ </xsd:annotation>
220
+ <xsd:simpleContent>
221
+ <xsd:restriction base="javaee:string"/>
222
+ </xsd:simpleContent>
223
+ </xsd:complexType>
224
+
225
+ <!-- **************************************************** -->
226
+
227
+ <xsd:complexType name="ejb-local-refType">
228
+ <xsd:annotation>
229
+ <xsd:documentation>
230
+
231
+ The ejb-local-refType is used by ejb-local-ref elements for
232
+ the declaration of a reference to an enterprise bean's local
233
+ home or to the local business interface of a 3.0 bean.
234
+ The declaration consists of:
235
+
236
+ - an optional description
237
+ - the EJB reference name used in the code of the Deployment
238
+ Component that's referencing the enterprise bean.
239
+ - the optional expected type of the referenced enterprise bean
240
+ - the optional expected local interface of the referenced
241
+ enterprise bean or the local business interface of the
242
+ referenced enterprise bean.
243
+ - the optional expected local home interface of the referenced
244
+ enterprise bean. Not applicable if this ejb-local-ref refers
245
+ to the local business interface of a 3.0 bean.
246
+ - optional ejb-link information, used to specify the
247
+ referenced enterprise bean
248
+ - optional elements to define injection of the named enterprise
249
+ bean into a component field or property.
250
+
251
+ </xsd:documentation>
252
+ </xsd:annotation>
253
+
254
+ <xsd:sequence>
255
+ <xsd:element name="description"
256
+ type="javaee:descriptionType"
257
+ minOccurs="0"
258
+ maxOccurs="unbounded"/>
259
+ <xsd:element name="ejb-ref-name"
260
+ type="javaee:ejb-ref-nameType"/>
261
+ <xsd:element name="ejb-ref-type"
262
+ type="javaee:ejb-ref-typeType"
263
+ minOccurs="0"/>
264
+ <xsd:element name="local-home"
265
+ type="javaee:local-homeType"
266
+ minOccurs="0"/>
267
+ <xsd:element name="local"
268
+ type="javaee:localType"
269
+ minOccurs="0"/>
270
+ <xsd:element name="ejb-link"
271
+ type="javaee:ejb-linkType"
272
+ minOccurs="0"/>
273
+ <xsd:group ref="javaee:resourceGroup"/>
274
+ </xsd:sequence>
275
+ <xsd:attribute name="id" type="xsd:ID"/>
276
+ </xsd:complexType>
277
+
278
+ <!-- **************************************************** -->
279
+
280
+ <xsd:complexType name="ejb-ref-nameType">
281
+ <xsd:annotation>
282
+ <xsd:documentation>
283
+ <![CDATA[
284
+
285
+ The ejb-ref-name element contains the name of an EJB
286
+ reference. The EJB reference is an entry in the
287
+ Deployment Component's environment and is relative to the
288
+ java:comp/env context. The name must be unique within the
289
+ Deployment Component.
290
+
291
+ It is recommended that name is prefixed with "ejb/".
292
+
293
+ Example:
294
+
295
+ <ejb-ref-name>ejb/Payroll</ejb-ref-name>
296
+
297
+ ]]>
298
+ </xsd:documentation>
299
+ </xsd:annotation>
300
+ <xsd:simpleContent>
301
+ <xsd:restriction base="javaee:jndi-nameType"/>
302
+ </xsd:simpleContent>
303
+ </xsd:complexType>
304
+
305
+ <!-- **************************************************** -->
306
+
307
+ <xsd:complexType name="ejb-ref-typeType">
308
+ <xsd:annotation>
309
+ <xsd:documentation>
310
+
311
+ The ejb-ref-typeType contains the expected type of the
312
+ referenced enterprise bean.
313
+
314
+ The ejb-ref-type designates a value
315
+ that must be one of the following:
316
+
317
+ Entity
318
+ Session
319
+
320
+ </xsd:documentation>
321
+ </xsd:annotation>
322
+ <xsd:simpleContent>
323
+ <xsd:restriction base="javaee:string">
324
+ <xsd:enumeration value="Entity"/>
325
+ <xsd:enumeration value="Session"/>
326
+ </xsd:restriction>
327
+ </xsd:simpleContent>
328
+ </xsd:complexType>
329
+
330
+ <!-- **************************************************** -->
331
+
332
+ <xsd:complexType name="ejb-refType">
333
+ <xsd:annotation>
334
+ <xsd:documentation>
335
+
336
+ The ejb-refType is used by ejb-ref elements for the
337
+ declaration of a reference to an enterprise bean's home or
338
+ to the remote business interface of a 3.0 bean.
339
+ The declaration consists of:
340
+
341
+ - an optional description
342
+ - the EJB reference name used in the code of
343
+ the Deployment Component that's referencing the enterprise
344
+ bean.
345
+ - the optional expected type of the referenced enterprise bean
346
+ - the optional remote interface of the referenced enterprise bean
347
+ or the remote business interface of the referenced enterprise
348
+ bean
349
+ - the optional expected home interface of the referenced
350
+ enterprise bean. Not applicable if this ejb-ref
351
+ refers to the remote business interface of a 3.0 bean.
352
+ - optional ejb-link information, used to specify the
353
+ referenced enterprise bean
354
+ - optional elements to define injection of the named enterprise
355
+ bean into a component field or property
356
+
357
+ </xsd:documentation>
358
+ </xsd:annotation>
359
+
360
+ <xsd:sequence>
361
+ <xsd:element name="description"
362
+ type="javaee:descriptionType"
363
+ minOccurs="0"
364
+ maxOccurs="unbounded"/>
365
+ <xsd:element name="ejb-ref-name"
366
+ type="javaee:ejb-ref-nameType"/>
367
+ <xsd:element name="ejb-ref-type"
368
+ type="javaee:ejb-ref-typeType"
369
+ minOccurs="0"/>
370
+ <xsd:element name="home"
371
+ type="javaee:homeType"
372
+ minOccurs="0"/>
373
+ <xsd:element name="remote"
374
+ type="javaee:remoteType"
375
+ minOccurs="0"/>
376
+ <xsd:element name="ejb-link"
377
+ type="javaee:ejb-linkType"
378
+ minOccurs="0"/>
379
+ <xsd:group ref="javaee:resourceGroup"/>
380
+ </xsd:sequence>
381
+ <xsd:attribute name="id" type="xsd:ID"/>
382
+ </xsd:complexType>
383
+
384
+ <!-- **************************************************** -->
385
+
386
+ <xsd:complexType name="emptyType">
387
+ <xsd:annotation>
388
+ <xsd:documentation>
389
+
390
+ This type is used to designate an empty
391
+ element when used.
392
+
393
+ </xsd:documentation>
394
+ </xsd:annotation>
395
+ <xsd:attribute name="id" type="xsd:ID"/>
396
+ </xsd:complexType>
397
+
398
+ <!-- **************************************************** -->
399
+
400
+ <xsd:complexType name="env-entry-type-valuesType">
401
+ <xsd:annotation>
402
+ <xsd:documentation>
403
+ <![CDATA[
404
+
405
+ This type contains the fully-qualified Java type of the
406
+ environment entry value that is expected by the
407
+ application's code.
408
+
409
+ The following are the legal values of env-entry-type-valuesType:
410
+
411
+ java.lang.Boolean
412
+ java.lang.Byte
413
+ java.lang.Character
414
+ java.lang.String
415
+ java.lang.Short
416
+ java.lang.Integer
417
+ java.lang.Long
418
+ java.lang.Float
419
+ java.lang.Double
420
+
421
+ Example:
422
+
423
+ <env-entry-type>java.lang.Boolean</env-entry-type>
424
+
425
+ ]]>
426
+ </xsd:documentation>
427
+ </xsd:annotation>
428
+ <xsd:simpleContent>
429
+ <xsd:restriction base="javaee:string">
430
+ <xsd:enumeration value="java.lang.Boolean"/>
431
+ <xsd:enumeration value="java.lang.Byte"/>
432
+ <xsd:enumeration value="java.lang.Character"/>
433
+ <xsd:enumeration value="java.lang.String"/>
434
+ <xsd:enumeration value="java.lang.Short"/>
435
+ <xsd:enumeration value="java.lang.Integer"/>
436
+ <xsd:enumeration value="java.lang.Long"/>
437
+ <xsd:enumeration value="java.lang.Float"/>
438
+ <xsd:enumeration value="java.lang.Double"/>
439
+ </xsd:restriction>
440
+ </xsd:simpleContent>
441
+ </xsd:complexType>
442
+
443
+ <!-- **************************************************** -->
444
+
445
+ <xsd:complexType name="env-entryType">
446
+ <xsd:annotation>
447
+ <xsd:documentation>
448
+
449
+ The env-entryType is used to declare an application's
450
+ environment entry. The declaration consists of an optional
451
+ description, the name of the environment entry, a type
452
+ (optional if the value is injected, otherwise required), and
453
+ an optional value.
454
+
455
+ It also includes optional elements to define injection of
456
+ the named resource into fields or JavaBeans properties.
457
+
458
+ If a value is not specified and injection is requested,
459
+ no injection will occur and no entry of the specified name
460
+ will be created. This allows an initial value to be
461
+ specified in the source code without being incorrectly
462
+ changed when no override has been specified.
463
+
464
+ If a value is not specified and no injection is requested,
465
+ a value must be supplied during deployment.
466
+
467
+ This type is used by env-entry elements.
468
+
469
+ </xsd:documentation>
470
+ </xsd:annotation>
471
+
472
+ <xsd:sequence>
473
+ <xsd:element name="description"
474
+ type="javaee:descriptionType"
475
+ minOccurs="0"
476
+ maxOccurs="unbounded"/>
477
+ <xsd:element name="env-entry-name"
478
+ type="javaee:jndi-nameType">
479
+ <xsd:annotation>
480
+ <xsd:documentation>
481
+ <![CDATA[
482
+
483
+ The env-entry-name element contains the name of a
484
+ Deployment Component's environment entry. The name
485
+ is a JNDI name relative to the java:comp/env
486
+ context. The name must be unique within a
487
+ Deployment Component. The uniqueness
488
+ constraints must be defined within the declared
489
+ context.
490
+
491
+ Example:
492
+
493
+ <env-entry-name>minAmount</env-entry-name>
494
+
495
+ ]]>
496
+ </xsd:documentation>
497
+ </xsd:annotation>
498
+ </xsd:element>
499
+
500
+ <xsd:element name="env-entry-type"
501
+ type="javaee:env-entry-type-valuesType"
502
+ minOccurs="0">
503
+ <xsd:annotation>
504
+ <xsd:documentation>
505
+ <![CDATA[
506
+
507
+ The env-entry-type element contains the Java language
508
+ type of the environment entry. If an injection target
509
+ is specified for the environment entry, the type may
510
+ be omitted, or must match the type of the injection
511
+ target. If no injection target is specified, the type
512
+ is required.
513
+
514
+ Example:
515
+
516
+ <env-entry-type>java.lang.Integer</env-entry-type>
517
+
518
+ ]]>
519
+ </xsd:documentation>
520
+ </xsd:annotation>
521
+ </xsd:element>
522
+
523
+ <xsd:element name="env-entry-value"
524
+ type="javaee:xsdStringType"
525
+ minOccurs="0">
526
+ <xsd:annotation>
527
+ <xsd:documentation>
528
+ <![CDATA[
529
+
530
+ The env-entry-value designates the value of a
531
+ Deployment Component's environment entry. The value
532
+ must be a String that is valid for the
533
+ constructor of the specified type that takes a
534
+ single String parameter, or for java.lang.Character,
535
+ a single character.
536
+
537
+ Example:
538
+
539
+ <env-entry-value>100.00</env-entry-value>
540
+
541
+ ]]>
542
+ </xsd:documentation>
543
+ </xsd:annotation>
544
+ </xsd:element>
545
+
546
+ <xsd:group ref="javaee:resourceGroup"/>
547
+
548
+ </xsd:sequence>
549
+ <xsd:attribute name="id" type="xsd:ID"/>
550
+ </xsd:complexType>
551
+
552
+ <!-- **************************************************** -->
553
+
554
+ <xsd:complexType name="fully-qualified-classType">
555
+ <xsd:annotation>
556
+ <xsd:documentation>
557
+
558
+ The elements that use this type designate the name of a
559
+ Java class or interface. The name is in the form of a
560
+ "binary name", as defined in the JLS. This is the form
561
+ of name used in Class.forName(). Tools that need the
562
+ canonical name (the name used in source code) will need
563
+ to convert this binary name to the canonical name.
564
+
565
+ </xsd:documentation>
566
+ </xsd:annotation>
567
+ <xsd:simpleContent>
568
+ <xsd:restriction base="javaee:string"/>
569
+ </xsd:simpleContent>
570
+ </xsd:complexType>
571
+
572
+ <!-- **************************************************** -->
573
+
574
+ <xsd:complexType name="generic-booleanType">
575
+ <xsd:annotation>
576
+ <xsd:documentation>
577
+
578
+ This type defines four different values which can designate
579
+ boolean values. This includes values yes and no which are
580
+ not designated by xsd:boolean
581
+
582
+ </xsd:documentation>
583
+ </xsd:annotation>
584
+ <xsd:simpleContent>
585
+ <xsd:restriction base="javaee:string">
586
+ <xsd:enumeration value="true"/>
587
+ <xsd:enumeration value="false"/>
588
+ <xsd:enumeration value="yes"/>
589
+ <xsd:enumeration value="no"/>
590
+ </xsd:restriction>
591
+ </xsd:simpleContent>
592
+ </xsd:complexType>
593
+
594
+ <!-- **************************************************** -->
595
+
596
+ <xsd:complexType name="homeType">
597
+ <xsd:annotation>
598
+ <xsd:documentation>
599
+ <![CDATA[
600
+
601
+ The homeType defines the fully-qualified name of
602
+ an enterprise bean's home interface.
603
+
604
+ Example:
605
+
606
+ <home>com.aardvark.payroll.PayrollHome</home>
607
+
608
+ ]]>
609
+ </xsd:documentation>
610
+ </xsd:annotation>
611
+ <xsd:simpleContent>
612
+ <xsd:restriction base="javaee:fully-qualified-classType"/>
613
+ </xsd:simpleContent>
614
+ </xsd:complexType>
615
+
616
+ <!-- **************************************************** -->
617
+
618
+ <xsd:complexType name="iconType">
619
+ <xsd:annotation>
620
+ <xsd:documentation>
621
+
622
+ The icon type contains small-icon and large-icon elements
623
+ that specify the file names for small and large GIF, JPEG,
624
+ or PNG icon images used to represent the parent element in a
625
+ GUI tool.
626
+
627
+ The xml:lang attribute defines the language that the
628
+ icon file names are provided in. Its value is "en" (English)
629
+ by default.
630
+
631
+ </xsd:documentation>
632
+ </xsd:annotation>
633
+
634
+ <xsd:sequence>
635
+ <xsd:element name="small-icon" type="javaee:pathType"
636
+ minOccurs="0">
637
+ <xsd:annotation>
638
+ <xsd:documentation>
639
+ <![CDATA[
640
+
641
+ The small-icon element contains the name of a file
642
+ containing a small (16 x 16) icon image. The file
643
+ name is a relative path within the Deployment
644
+ Component's Deployment File.
645
+
646
+ The image may be in the GIF, JPEG, or PNG format.
647
+ The icon can be used by tools.
648
+
649
+ Example:
650
+
651
+ <small-icon>employee-service-icon16x16.jpg</small-icon>
652
+
653
+ ]]>
654
+ </xsd:documentation>
655
+ </xsd:annotation>
656
+ </xsd:element>
657
+ <xsd:element name="large-icon" type="javaee:pathType"
658
+ minOccurs="0">
659
+ <xsd:annotation>
660
+ <xsd:documentation>
661
+ <![CDATA[
662
+
663
+ The large-icon element contains the name of a file
664
+ containing a large
665
+ (32 x 32) icon image. The file name is a relative
666
+ path within the Deployment Component's Deployment
667
+ File.
668
+
669
+ The image may be in the GIF, JPEG, or PNG format.
670
+ The icon can be used by tools.
671
+
672
+ Example:
673
+
674
+ <large-icon>employee-service-icon32x32.jpg</large-icon>
675
+
676
+ ]]>
677
+ </xsd:documentation>
678
+ </xsd:annotation>
679
+ </xsd:element>
680
+
681
+ </xsd:sequence>
682
+
683
+ <xsd:attribute ref="xml:lang"/>
684
+ <xsd:attribute name="id" type="xsd:ID"/>
685
+
686
+ </xsd:complexType>
687
+
688
+ <!-- **************************************************** -->
689
+
690
+ <xsd:complexType name="injection-targetType">
691
+ <xsd:annotation>
692
+ <xsd:documentation>
693
+
694
+ An injection target specifies a class and a name within
695
+ that class into which a resource should be injected.
696
+
697
+ The injection target class specifies the fully qualified
698
+ class name that is the target of the injection. The
699
+ Java EE specifications describe which classes can be an
700
+ injection target.
701
+
702
+ The injection target name specifies the target within
703
+ the specified class. The target is first looked for as a
704
+ JavaBeans property name. If not found, the target is
705
+ looked for as a field name.
706
+
707
+ The specified resource will be injected into the target
708
+ during initialization of the class by either calling the
709
+ set method for the target property or by setting a value
710
+ into the named field.
711
+
712
+ </xsd:documentation>
713
+ </xsd:annotation>
714
+ <xsd:sequence>
715
+ <xsd:element name="injection-target-class"
716
+ type="javaee:fully-qualified-classType"/>
717
+ <xsd:element name="injection-target-name"
718
+ type="javaee:java-identifierType"/>
719
+ </xsd:sequence>
720
+ </xsd:complexType>
721
+
722
+ <!-- **************************************************** -->
723
+
724
+ <xsd:complexType name="java-identifierType">
725
+ <xsd:annotation>
726
+ <xsd:documentation>
727
+
728
+ The java-identifierType defines a Java identifier.
729
+ The users of this type should further verify that
730
+ the content does not contain Java reserved keywords.
731
+
732
+ </xsd:documentation>
733
+ </xsd:annotation>
734
+ <xsd:simpleContent>
735
+ <xsd:restriction base="javaee:string">
736
+ <xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/>
737
+ </xsd:restriction>
738
+ </xsd:simpleContent>
739
+ </xsd:complexType>
740
+
741
+ <!-- **************************************************** -->
742
+
743
+ <xsd:complexType name="java-typeType">
744
+ <xsd:annotation>
745
+ <xsd:documentation>
746
+
747
+ This is a generic type that designates a Java primitive
748
+ type or a fully qualified name of a Java interface/type,
749
+ or an array of such types.
750
+
751
+ </xsd:documentation>
752
+ </xsd:annotation>
753
+ <xsd:simpleContent>
754
+ <xsd:restriction base="javaee:string">
755
+ <xsd:pattern value="[^\p{Z}]*"/>
756
+ </xsd:restriction>
757
+ </xsd:simpleContent>
758
+ </xsd:complexType>
759
+
760
+ <!-- **************************************************** -->
761
+
762
+ <xsd:complexType name="jndi-nameType">
763
+ <xsd:annotation>
764
+ <xsd:documentation>
765
+
766
+ The jndi-nameType type designates a JNDI name in the
767
+ Deployment Component's environment and is relative to the
768
+ java:comp/env context. A JNDI name must be unique within the
769
+ Deployment Component.
770
+
771
+ </xsd:documentation>
772
+ </xsd:annotation>
773
+ <xsd:simpleContent>
774
+ <xsd:restriction base="javaee:string"/>
775
+ </xsd:simpleContent>
776
+ </xsd:complexType>
777
+
778
+ <!-- **************************************************** -->
779
+
780
+ <xsd:group name="jndiEnvironmentRefsGroup">
781
+ <xsd:annotation>
782
+ <xsd:documentation>
783
+
784
+ This group keeps the usage of the contained JNDI environment
785
+ reference elements consistent across Java EE deployment descriptors.
786
+
787
+ </xsd:documentation>
788
+ </xsd:annotation>
789
+ <xsd:sequence>
790
+ <xsd:element name="env-entry"
791
+ type="javaee:env-entryType"
792
+ minOccurs="0" maxOccurs="unbounded"/>
793
+ <xsd:element name="ejb-ref"
794
+ type="javaee:ejb-refType"
795
+ minOccurs="0" maxOccurs="unbounded"/>
796
+ <xsd:element name="ejb-local-ref"
797
+ type="javaee:ejb-local-refType"
798
+ minOccurs="0" maxOccurs="unbounded"/>
799
+ <xsd:group ref="javaee:service-refGroup"/>
800
+ <xsd:element name="resource-ref"
801
+ type="javaee:resource-refType"
802
+ minOccurs="0" maxOccurs="unbounded"/>
803
+ <xsd:element name="resource-env-ref"
804
+ type="javaee:resource-env-refType"
805
+ minOccurs="0" maxOccurs="unbounded"/>
806
+ <xsd:element name="message-destination-ref"
807
+ type="javaee:message-destination-refType"
808
+ minOccurs="0" maxOccurs="unbounded"/>
809
+ <xsd:element name="persistence-context-ref"
810
+ type="javaee:persistence-context-refType"
811
+ minOccurs="0" maxOccurs="unbounded"/>
812
+ <xsd:element name="persistence-unit-ref"
813
+ type="javaee:persistence-unit-refType"
814
+ minOccurs="0" maxOccurs="unbounded"/>
815
+ <xsd:element name="post-construct"
816
+ type="javaee:lifecycle-callbackType"
817
+ minOccurs="0" maxOccurs="unbounded"/>
818
+ <xsd:element name="pre-destroy"
819
+ type="javaee:lifecycle-callbackType"
820
+ minOccurs="0" maxOccurs="unbounded"/>
821
+ </xsd:sequence>
822
+ </xsd:group>
823
+
824
+ <!-- **************************************************** -->
825
+
826
+ <xsd:complexType name="lifecycle-callbackType">
827
+ <xsd:annotation>
828
+ <xsd:documentation>
829
+
830
+ The lifecycle-callback type specifies a method on a
831
+ class to be called when a lifecycle event occurs.
832
+ Note that each class may have only one lifecycle callback
833
+ method for any given event and that the method may not
834
+ be overloaded.
835
+
836
+ If the lifefycle-callback-class element is missing then
837
+ the class defining the callback is assumed to be the
838
+ component class in scope at the place in the descriptor
839
+ in which the callback definition appears.
840
+
841
+ </xsd:documentation>
842
+ </xsd:annotation>
843
+ <xsd:sequence>
844
+ <xsd:element name="lifecycle-callback-class"
845
+ type="javaee:fully-qualified-classType"
846
+ minOccurs="0"/>
847
+ <xsd:element name="lifecycle-callback-method"
848
+ type="javaee:java-identifierType"/>
849
+ </xsd:sequence>
850
+ </xsd:complexType>
851
+
852
+ <!-- **************************************************** -->
853
+
854
+ <xsd:complexType name="listenerType">
855
+ <xsd:annotation>
856
+ <xsd:documentation>
857
+
858
+ The listenerType indicates the deployment properties for a web
859
+ application listener bean.
860
+
861
+ </xsd:documentation>
862
+ </xsd:annotation>
863
+
864
+ <xsd:sequence>
865
+ <xsd:group ref="javaee:descriptionGroup"/>
866
+ <xsd:element name="listener-class"
867
+ type="javaee:fully-qualified-classType">
868
+ <xsd:annotation>
869
+ <xsd:documentation>
870
+
871
+ The listener-class element declares a class in the
872
+ application must be registered as a web
873
+ application listener bean. The value is the fully
874
+ qualified classname of the listener class.
875
+
876
+ </xsd:documentation>
877
+ </xsd:annotation>
878
+ </xsd:element>
879
+ </xsd:sequence>
880
+ <xsd:attribute name="id" type="xsd:ID"/>
881
+ </xsd:complexType>
882
+
883
+ <!-- **************************************************** -->
884
+
885
+ <xsd:complexType name="local-homeType">
886
+ <xsd:annotation>
887
+ <xsd:documentation>
888
+
889
+ The local-homeType defines the fully-qualified
890
+ name of an enterprise bean's local home interface.
891
+
892
+ </xsd:documentation>
893
+ </xsd:annotation>
894
+ <xsd:simpleContent>
895
+ <xsd:restriction base="javaee:fully-qualified-classType"/>
896
+ </xsd:simpleContent>
897
+ </xsd:complexType>
898
+
899
+ <!-- **************************************************** -->
900
+
901
+ <xsd:complexType name="localType">
902
+ <xsd:annotation>
903
+ <xsd:documentation>
904
+
905
+ The localType defines the fully-qualified name of an
906
+ enterprise bean's local interface.
907
+
908
+ </xsd:documentation>
909
+ </xsd:annotation>
910
+ <xsd:simpleContent>
911
+ <xsd:restriction base="javaee:fully-qualified-classType"/>
912
+ </xsd:simpleContent>
913
+ </xsd:complexType>
914
+
915
+ <!-- **************************************************** -->
916
+
917
+ <xsd:complexType name="message-destination-linkType">
918
+ <xsd:annotation>
919
+ <xsd:documentation>
920
+
921
+ The message-destination-linkType is used to link a message
922
+ destination reference or message-driven bean to a message
923
+ destination.
924
+
925
+ The Assembler sets the value to reflect the flow of messages
926
+ between producers and consumers in the application.
927
+
928
+ The value must be the message-destination-name of a message
929
+ destination in the same Deployment File or in another
930
+ Deployment File in the same Java EE application unit.
931
+
932
+ Alternatively, the value may be composed of a path name
933
+ specifying a Deployment File containing the referenced
934
+ message destination with the message-destination-name of the
935
+ destination appended and separated from the path name by
936
+ "#". The path name is relative to the Deployment File
937
+ containing Deployment Component that is referencing the
938
+ message destination. This allows multiple message
939
+ destinations with the same name to be uniquely identified.
940
+
941
+ </xsd:documentation>
942
+ </xsd:annotation>
943
+ <xsd:simpleContent>
944
+ <xsd:restriction base="javaee:string"/>
945
+ </xsd:simpleContent>
946
+ </xsd:complexType>
947
+
948
+ <!-- **************************************************** -->
949
+
950
+ <xsd:complexType name="message-destination-refType">
951
+ <xsd:annotation>
952
+ <xsd:documentation>
953
+ <![CDATA[
954
+
955
+ The message-destination-ref element contains a declaration
956
+ of Deployment Component's reference to a message destination
957
+ associated with a resource in Deployment Component's
958
+ environment. It consists of:
959
+
960
+ - an optional description
961
+ - the message destination reference name
962
+ - an optional message destination type
963
+ - an optional specification as to whether
964
+ the destination is used for
965
+ consuming or producing messages, or both.
966
+ if not specified, "both" is assumed.
967
+ - an optional link to the message destination
968
+ - optional injection targets
969
+
970
+ The message destination type must be supplied unless an
971
+ injection target is specified, in which case the type
972
+ of the target is used. If both are specified, the type
973
+ must be assignment compatible with the type of the injection
974
+ target.
975
+
976
+ Examples:
977
+
978
+ <message-destination-ref>
979
+ <message-destination-ref-name>jms/StockQueue
980
+ </message-destination-ref-name>
981
+ <message-destination-type>javax.jms.Queue
982
+ </message-destination-type>
983
+ <message-destination-usage>Consumes
984
+ </message-destination-usage>
985
+ <message-destination-link>CorporateStocks
986
+ </message-destination-link>
987
+ </message-destination-ref>
988
+
989
+ ]]>
990
+ </xsd:documentation>
991
+ </xsd:annotation>
992
+ <xsd:sequence>
993
+ <xsd:element name="description"
994
+ type="javaee:descriptionType"
995
+ minOccurs="0"
996
+ maxOccurs="unbounded"/>
997
+ <xsd:element name="message-destination-ref-name"
998
+ type="javaee:jndi-nameType">
999
+ <xsd:annotation>
1000
+ <xsd:documentation>
1001
+
1002
+ The message-destination-ref-name element specifies
1003
+ the name of a message destination reference; its
1004
+ value is the environment entry name used in
1005
+ Deployment Component code. The name is a JNDI name
1006
+ relative to the java:comp/env context and must be
1007
+ unique within an ejb-jar (for enterprise beans) or a
1008
+ Deployment File (for others).
1009
+
1010
+ </xsd:documentation>
1011
+ </xsd:annotation>
1012
+ </xsd:element>
1013
+ <xsd:element name="message-destination-type"
1014
+ type="javaee:message-destination-typeType"
1015
+ minOccurs="0"/>
1016
+ <xsd:element name="message-destination-usage"
1017
+ type="javaee:message-destination-usageType"
1018
+ minOccurs="0"/>
1019
+ <xsd:element name="message-destination-link"
1020
+ type="javaee:message-destination-linkType"
1021
+ minOccurs="0"/>
1022
+
1023
+ <xsd:group ref="javaee:resourceGroup"/>
1024
+
1025
+ </xsd:sequence>
1026
+ <xsd:attribute name="id" type="xsd:ID"/>
1027
+
1028
+ </xsd:complexType>
1029
+
1030
+ <!-- **************************************************** -->
1031
+
1032
+ <xsd:complexType name="message-destination-typeType">
1033
+ <xsd:annotation>
1034
+ <xsd:documentation>
1035
+ <![CDATA[
1036
+
1037
+ The message-destination-typeType specifies the type of
1038
+ the destination. The type is specified by the Java interface
1039
+ expected to be implemented by the destination.
1040
+
1041
+ Example:
1042
+
1043
+ <message-destination-type>javax.jms.Queue
1044
+ </message-destination-type>
1045
+
1046
+ ]]>
1047
+ </xsd:documentation>
1048
+ </xsd:annotation>
1049
+ <xsd:simpleContent>
1050
+ <xsd:restriction base="javaee:fully-qualified-classType"/>
1051
+ </xsd:simpleContent>
1052
+ </xsd:complexType>
1053
+
1054
+ <!-- **************************************************** -->
1055
+
1056
+ <xsd:complexType name="message-destination-usageType">
1057
+ <xsd:annotation>
1058
+ <xsd:documentation>
1059
+
1060
+ The message-destination-usageType specifies the use of the
1061
+ message destination indicated by the reference. The value
1062
+ indicates whether messages are consumed from the message
1063
+ destination, produced for the destination, or both. The
1064
+ Assembler makes use of this information in linking producers
1065
+ of a destination with its consumers.
1066
+
1067
+ The value of the message-destination-usage element must be
1068
+ one of the following:
1069
+ Consumes
1070
+ Produces
1071
+ ConsumesProduces
1072
+
1073
+ </xsd:documentation>
1074
+ </xsd:annotation>
1075
+ <xsd:simpleContent>
1076
+ <xsd:restriction base="javaee:string">
1077
+ <xsd:enumeration value="Consumes"/>
1078
+ <xsd:enumeration value="Produces"/>
1079
+ <xsd:enumeration value="ConsumesProduces"/>
1080
+ </xsd:restriction>
1081
+ </xsd:simpleContent>
1082
+ </xsd:complexType>
1083
+
1084
+ <!-- **************************************************** -->
1085
+
1086
+ <xsd:complexType name="message-destinationType">
1087
+ <xsd:annotation>
1088
+ <xsd:documentation>
1089
+ <![CDATA[
1090
+
1091
+ The message-destinationType specifies a message
1092
+ destination. The logical destination described by this
1093
+ element is mapped to a physical destination by the Deployer.
1094
+
1095
+ The message destination element contains:
1096
+
1097
+ - an optional description
1098
+ - an optional display-name
1099
+ - an optional icon
1100
+ - a message destination name which must be unique
1101
+ among message destination names within the same
1102
+ Deployment File.
1103
+ - an optional mapped name
1104
+
1105
+ Example:
1106
+
1107
+ <message-destination>
1108
+ <message-destination-name>CorporateStocks
1109
+ </message-destination-name>
1110
+ </message-destination>
1111
+
1112
+ ]]>
1113
+ </xsd:documentation>
1114
+ </xsd:annotation>
1115
+ <xsd:sequence>
1116
+ <xsd:group ref="javaee:descriptionGroup"/>
1117
+ <xsd:element name="message-destination-name"
1118
+ type="javaee:string">
1119
+ <xsd:annotation>
1120
+ <xsd:documentation>
1121
+
1122
+ The message-destination-name element specifies a
1123
+ name for a message destination. This name must be
1124
+ unique among the names of message destinations
1125
+ within the Deployment File.
1126
+
1127
+ </xsd:documentation>
1128
+ </xsd:annotation>
1129
+ </xsd:element>
1130
+ <xsd:element name="mapped-name"
1131
+ type="javaee:xsdStringType"
1132
+ minOccurs="0">
1133
+ <xsd:annotation>
1134
+ <xsd:documentation>
1135
+ <![CDATA[
1136
+
1137
+ A product specific name that this message destination
1138
+ should be mapped to. Each message-destination-ref
1139
+ element that references this message destination will
1140
+ define a name in the namespace of the referencing
1141
+ component. (It's a name in the JNDI java:comp/env
1142
+ namespace.) Many application servers provide a way to
1143
+ map these local names to names of resources known to the
1144
+ application server. This mapped name is often a global
1145
+ JNDI name, but may be a name of any form. Each of the
1146
+ local names should be mapped to this same global name.
1147
+
1148
+ Application servers are not required to support any
1149
+ particular form or type of mapped name, nor the ability
1150
+ to use mapped names. The mapped name is
1151
+ product-dependent and often installation-dependent. No
1152
+ use of a mapped name is portable.
1153
+
1154
+ ]]>
1155
+ </xsd:documentation>
1156
+ </xsd:annotation>
1157
+ </xsd:element>
1158
+ </xsd:sequence>
1159
+ <xsd:attribute name="id" type="xsd:ID"/>
1160
+ </xsd:complexType>
1161
+
1162
+ <!-- **************************************************** -->
1163
+
1164
+ <xsd:complexType name="param-valueType">
1165
+ <xsd:annotation>
1166
+ <xsd:documentation>
1167
+
1168
+ This type is a general type that can be used to declare
1169
+ parameter/value lists.
1170
+
1171
+ </xsd:documentation>
1172
+ </xsd:annotation>
1173
+
1174
+ <xsd:sequence>
1175
+ <xsd:element name="description"
1176
+ type="javaee:descriptionType"
1177
+ minOccurs="0"
1178
+ maxOccurs="unbounded"/>
1179
+ <xsd:element name="param-name"
1180
+ type="javaee:string">
1181
+ <xsd:annotation>
1182
+ <xsd:documentation>
1183
+
1184
+ The param-name element contains the name of a
1185
+ parameter.
1186
+
1187
+ </xsd:documentation>
1188
+ </xsd:annotation>
1189
+ </xsd:element>
1190
+
1191
+ <xsd:element name="param-value"
1192
+ type="javaee:xsdStringType">
1193
+ <xsd:annotation>
1194
+ <xsd:documentation>
1195
+
1196
+ The param-value element contains the value of a
1197
+ parameter.
1198
+
1199
+ </xsd:documentation>
1200
+ </xsd:annotation>
1201
+ </xsd:element>
1202
+ </xsd:sequence>
1203
+ <xsd:attribute name="id" type="xsd:ID"/>
1204
+ </xsd:complexType>
1205
+
1206
+ <!-- **************************************************** -->
1207
+
1208
+ <xsd:complexType name="pathType">
1209
+ <xsd:annotation>
1210
+ <xsd:documentation>
1211
+
1212
+ The elements that use this type designate either a relative
1213
+ path or an absolute path starting with a "/".
1214
+
1215
+ In elements that specify a pathname to a file within the
1216
+ same Deployment File, relative filenames (i.e., those not
1217
+ starting with "/") are considered relative to the root of
1218
+ the Deployment File's namespace. Absolute filenames (i.e.,
1219
+ those starting with "/") also specify names in the root of
1220
+ the Deployment File's namespace. In general, relative names
1221
+ are preferred. The exception is .war files where absolute
1222
+ names are preferred for consistency with the Servlet API.
1223
+
1224
+ </xsd:documentation>
1225
+ </xsd:annotation>
1226
+ <xsd:simpleContent>
1227
+ <xsd:restriction base="javaee:string"/>
1228
+ </xsd:simpleContent>
1229
+ </xsd:complexType>
1230
+
1231
+ <!-- **************************************************** -->
1232
+
1233
+ <xsd:complexType name="persistence-context-refType">
1234
+ <xsd:annotation>
1235
+ <xsd:documentation>
1236
+ <![CDATA[
1237
+
1238
+ The persistence-context-ref element contains a declaration
1239
+ of Deployment Component's reference to a persistence context
1240
+ associated within a Deployment Component's
1241
+ environment. It consists of:
1242
+
1243
+ - an optional description
1244
+ - the persistence context reference name
1245
+ - an optional persistence unit name. If not specified,
1246
+ the default persistence unit is assumed.
1247
+ - an optional specification as to whether
1248
+ the persistence context type is Transaction or
1249
+ Extended. If not specified, Transaction is assumed.
1250
+ - an optional list of persistence properties
1251
+ - optional injection targets
1252
+
1253
+ Examples:
1254
+
1255
+ <persistence-context-ref>
1256
+ <persistence-context-ref-name>myPersistenceContext
1257
+ </persistence-context-ref-name>
1258
+ </persistence-context-ref>
1259
+
1260
+ <persistence-context-ref>
1261
+ <persistence-context-ref-name>myPersistenceContext
1262
+ </persistence-context-ref-name>
1263
+ <persistence-unit-name>PersistenceUnit1
1264
+ </persistence-unit-name>
1265
+ <persistence-context-type>Extended</persistence-context-type>
1266
+ </persistence-context-ref>
1267
+
1268
+ ]]>
1269
+ </xsd:documentation>
1270
+ </xsd:annotation>
1271
+ <xsd:sequence>
1272
+ <xsd:element name="description"
1273
+ type="javaee:descriptionType"
1274
+ minOccurs="0"
1275
+ maxOccurs="unbounded"/>
1276
+ <xsd:element name="persistence-context-ref-name"
1277
+ type="javaee:jndi-nameType">
1278
+ <xsd:annotation>
1279
+ <xsd:documentation>
1280
+
1281
+ The persistence-context-ref-name element specifies
1282
+ the name of a persistence context reference; its
1283
+ value is the environment entry name used in
1284
+ Deployment Component code. The name is a JNDI name
1285
+ relative to the java:comp/env context.
1286
+
1287
+ </xsd:documentation>
1288
+ </xsd:annotation>
1289
+ </xsd:element>
1290
+ <xsd:element name="persistence-unit-name"
1291
+ type="javaee:string"
1292
+ minOccurs="0">
1293
+ <xsd:annotation>
1294
+ <xsd:documentation>
1295
+
1296
+ The Application Assembler(or BeanProvider) may use the
1297
+ following syntax to avoid the need to rename persistence
1298
+ units to have unique names within a Java EE application.
1299
+
1300
+ The Application Assembler specifies the pathname of the
1301
+ root of the persistence.xml file for the referenced
1302
+ persistence unit and appends the name of the persistence
1303
+ unit separated from the pathname by #. The pathname is
1304
+ relative to the referencing application component jar file.
1305
+ In this manner, multiple persistence units with the same
1306
+ persistence unit name may be uniquely identified when the
1307
+ Application Assembler cannot change persistence unit names.
1308
+
1309
+ </xsd:documentation>
1310
+ </xsd:annotation>
1311
+ </xsd:element>
1312
+
1313
+ <xsd:element name="persistence-context-type"
1314
+ type="javaee:persistence-context-typeType"
1315
+ minOccurs="0"/>
1316
+
1317
+ <xsd:element name="persistence-property"
1318
+ type="javaee:propertyType"
1319
+ minOccurs="0"
1320
+ maxOccurs="unbounded">
1321
+ <xsd:annotation>
1322
+ <xsd:documentation>
1323
+
1324
+ Used to specify properties for the container or persistence
1325
+ provider. Vendor-specific properties may be included in
1326
+ the set of properties. Properties that are not recognized
1327
+ by a vendor must be ignored. Entries that make use of the
1328
+ namespace javax.persistence and its subnamespaces must not
1329
+ be used for vendor-specific properties. The namespace
1330
+ javax.persistence is reserved for use by the specification.
1331
+
1332
+ </xsd:documentation>
1333
+ </xsd:annotation>
1334
+ </xsd:element>
1335
+
1336
+ <xsd:group ref="javaee:resourceGroup"/>
1337
+
1338
+ </xsd:sequence>
1339
+ <xsd:attribute name="id" type="xsd:ID"/>
1340
+
1341
+ </xsd:complexType>
1342
+
1343
+ <!-- **************************************************** -->
1344
+
1345
+ <xsd:complexType name="persistence-context-typeType">
1346
+ <xsd:annotation>
1347
+ <xsd:documentation>
1348
+
1349
+ The persistence-context-typeType specifies the transactional
1350
+ nature of a persistence context reference.
1351
+
1352
+ The value of the persistence-context-type element must be
1353
+ one of the following:
1354
+ Transaction
1355
+ Extended
1356
+
1357
+ </xsd:documentation>
1358
+ </xsd:annotation>
1359
+ <xsd:simpleContent>
1360
+ <xsd:restriction base="javaee:string">
1361
+ <xsd:enumeration value="Transaction"/>
1362
+ <xsd:enumeration value="Extended"/>
1363
+ </xsd:restriction>
1364
+ </xsd:simpleContent>
1365
+ </xsd:complexType>
1366
+
1367
+ <!-- **************************************************** -->
1368
+
1369
+ <xsd:complexType name="persistence-unit-refType">
1370
+ <xsd:annotation>
1371
+ <xsd:documentation>
1372
+ <![CDATA[
1373
+
1374
+ The persistence-unit-ref element contains a declaration
1375
+ of Deployment Component's reference to a persistence unit
1376
+ associated within a Deployment Component's
1377
+ environment. It consists of:
1378
+
1379
+ - an optional description
1380
+ - the persistence unit reference name
1381
+ - an optional persistence unit name. If not specified,
1382
+ the default persistence unit is assumed.
1383
+ - optional injection targets
1384
+
1385
+ Examples:
1386
+
1387
+ <persistence-unit-ref>
1388
+ <persistence-unit-ref-name>myPersistenceUnit
1389
+ </persistence-unit-ref-name>
1390
+ </persistence-unit-ref>
1391
+
1392
+ <persistence-unit-ref>
1393
+ <persistence-unit-ref-name>myPersistenceUnit
1394
+ </persistence-unit-ref-name>
1395
+ <persistence-unit-name>PersistenceUnit1
1396
+ </persistence-unit-name>
1397
+ </persistence-unit-ref>
1398
+
1399
+ ]]>
1400
+ </xsd:documentation>
1401
+ </xsd:annotation>
1402
+ <xsd:sequence>
1403
+ <xsd:element name="description"
1404
+ type="javaee:descriptionType"
1405
+ minOccurs="0"
1406
+ maxOccurs="unbounded"/>
1407
+ <xsd:element name="persistence-unit-ref-name"
1408
+ type="javaee:jndi-nameType">
1409
+ <xsd:annotation>
1410
+ <xsd:documentation>
1411
+
1412
+ The persistence-unit-ref-name element specifies
1413
+ the name of a persistence unit reference; its
1414
+ value is the environment entry name used in
1415
+ Deployment Component code. The name is a JNDI name
1416
+ relative to the java:comp/env context.
1417
+
1418
+ </xsd:documentation>
1419
+ </xsd:annotation>
1420
+ </xsd:element>
1421
+ <xsd:element name="persistence-unit-name"
1422
+ type="javaee:string"
1423
+ minOccurs="0">
1424
+ <xsd:annotation>
1425
+ <xsd:documentation>
1426
+
1427
+ The Application Assembler(or BeanProvider) may use the
1428
+ following syntax to avoid the need to rename persistence
1429
+ units to have unique names within a Java EE application.
1430
+
1431
+ The Application Assembler specifies the pathname of the
1432
+ root of the persistence.xml file for the referenced
1433
+ persistence unit and appends the name of the persistence
1434
+ unit separated from the pathname by #. The pathname is
1435
+ relative to the referencing application component jar file.
1436
+ In this manner, multiple persistence units with the same
1437
+ persistence unit name may be uniquely identified when the
1438
+ Application Assembler cannot change persistence unit names.
1439
+
1440
+ </xsd:documentation>
1441
+ </xsd:annotation>
1442
+ </xsd:element>
1443
+
1444
+ <xsd:group ref="javaee:resourceGroup"/>
1445
+
1446
+ </xsd:sequence>
1447
+ <xsd:attribute name="id" type="xsd:ID"/>
1448
+
1449
+ </xsd:complexType>
1450
+
1451
+ <!-- **************************************************** -->
1452
+
1453
+ <xsd:complexType name="propertyType">
1454
+ <xsd:annotation>
1455
+ <xsd:documentation>
1456
+
1457
+ Specifies a name/value pair.
1458
+
1459
+ </xsd:documentation>
1460
+ </xsd:annotation>
1461
+
1462
+ <xsd:sequence>
1463
+ <xsd:element name="name"
1464
+ type="javaee:xsdStringType">
1465
+ </xsd:element>
1466
+ <xsd:element name="value"
1467
+ type="javaee:xsdStringType">
1468
+ </xsd:element>
1469
+ </xsd:sequence>
1470
+ <xsd:attribute name="id" type="xsd:ID"/>
1471
+ </xsd:complexType>
1472
+
1473
+ <!-- **************************************************** -->
1474
+
1475
+ <xsd:complexType name="remoteType">
1476
+ <xsd:annotation>
1477
+ <xsd:documentation>
1478
+ <![CDATA[
1479
+
1480
+ The remote element contains the fully-qualified name
1481
+ of the enterprise bean's remote interface.
1482
+
1483
+ Example:
1484
+
1485
+ <remote>com.wombat.empl.EmployeeService</remote>
1486
+
1487
+ ]]>
1488
+ </xsd:documentation>
1489
+ </xsd:annotation>
1490
+ <xsd:simpleContent>
1491
+ <xsd:restriction base="javaee:fully-qualified-classType"/>
1492
+ </xsd:simpleContent>
1493
+ </xsd:complexType>
1494
+
1495
+ <!-- **************************************************** -->
1496
+
1497
+ <xsd:complexType name="res-authType">
1498
+ <xsd:annotation>
1499
+ <xsd:documentation>
1500
+
1501
+ The res-authType specifies whether the Deployment Component
1502
+ code signs on programmatically to the resource manager, or
1503
+ whether the Container will sign on to the resource manager
1504
+ on behalf of the Deployment Component. In the latter case,
1505
+ the Container uses information that is supplied by the
1506
+ Deployer.
1507
+
1508
+ The value must be one of the two following:
1509
+
1510
+ Application
1511
+ Container
1512
+
1513
+ </xsd:documentation>
1514
+ </xsd:annotation>
1515
+ <xsd:simpleContent>
1516
+ <xsd:restriction base="javaee:string">
1517
+ <xsd:enumeration value="Application"/>
1518
+ <xsd:enumeration value="Container"/>
1519
+ </xsd:restriction>
1520
+ </xsd:simpleContent>
1521
+ </xsd:complexType>
1522
+
1523
+ <!-- **************************************************** -->
1524
+
1525
+ <xsd:complexType name="res-sharing-scopeType">
1526
+ <xsd:annotation>
1527
+ <xsd:documentation>
1528
+
1529
+ The res-sharing-scope type specifies whether connections
1530
+ obtained through the given resource manager connection
1531
+ factory reference can be shared. The value, if specified,
1532
+ must be one of the two following:
1533
+
1534
+ Shareable
1535
+ Unshareable
1536
+
1537
+ The default value is Shareable.
1538
+
1539
+ </xsd:documentation>
1540
+ </xsd:annotation>
1541
+ <xsd:simpleContent>
1542
+ <xsd:restriction base="javaee:string">
1543
+ <xsd:enumeration value="Shareable"/>
1544
+ <xsd:enumeration value="Unshareable"/>
1545
+ </xsd:restriction>
1546
+ </xsd:simpleContent>
1547
+ </xsd:complexType>
1548
+
1549
+ <!-- **************************************************** -->
1550
+
1551
+ <xsd:complexType name="resource-env-refType">
1552
+ <xsd:annotation>
1553
+ <xsd:documentation>
1554
+ <![CDATA[
1555
+
1556
+ The resource-env-refType is used to define
1557
+ resource-env-type elements. It contains a declaration of a
1558
+ Deployment Component's reference to an administered object
1559
+ associated with a resource in the Deployment Component's
1560
+ environment. It consists of an optional description, the
1561
+ resource environment reference name, and an optional
1562
+ indication of the resource environment reference type
1563
+ expected by the Deployment Component code.
1564
+
1565
+ It also includes optional elements to define injection of
1566
+ the named resource into fields or JavaBeans properties.
1567
+
1568
+ The resource environment type must be supplied unless an
1569
+ injection target is specified, in which case the type
1570
+ of the target is used. If both are specified, the type
1571
+ must be assignment compatible with the type of the injection
1572
+ target.
1573
+
1574
+ Example:
1575
+
1576
+ <resource-env-ref>
1577
+ <resource-env-ref-name>jms/StockQueue
1578
+ </resource-env-ref-name>
1579
+ <resource-env-ref-type>javax.jms.Queue
1580
+ </resource-env-ref-type>
1581
+ </resource-env-ref>
1582
+
1583
+ ]]>
1584
+ </xsd:documentation>
1585
+ </xsd:annotation>
1586
+
1587
+ <xsd:sequence>
1588
+ <xsd:element name="description"
1589
+ type="javaee:descriptionType"
1590
+ minOccurs="0"
1591
+ maxOccurs="unbounded"/>
1592
+ <xsd:element name="resource-env-ref-name"
1593
+ type="javaee:jndi-nameType">
1594
+ <xsd:annotation>
1595
+ <xsd:documentation>
1596
+
1597
+ The resource-env-ref-name element specifies the name
1598
+ of a resource environment reference; its value is
1599
+ the environment entry name used in
1600
+ the Deployment Component code. The name is a JNDI
1601
+ name relative to the java:comp/env context and must
1602
+ be unique within a Deployment Component.
1603
+
1604
+ </xsd:documentation>
1605
+ </xsd:annotation>
1606
+ </xsd:element>
1607
+
1608
+ <xsd:element name="resource-env-ref-type"
1609
+ type="javaee:fully-qualified-classType"
1610
+ minOccurs="0">
1611
+ <xsd:annotation>
1612
+ <xsd:documentation>
1613
+
1614
+ The resource-env-ref-type element specifies the type
1615
+ of a resource environment reference. It is the
1616
+ fully qualified name of a Java language class or
1617
+ interface.
1618
+
1619
+ </xsd:documentation>
1620
+ </xsd:annotation>
1621
+ </xsd:element>
1622
+
1623
+ <xsd:group ref="javaee:resourceGroup"/>
1624
+
1625
+ </xsd:sequence>
1626
+ <xsd:attribute name="id" type="xsd:ID"/>
1627
+ </xsd:complexType>
1628
+
1629
+ <!-- **************************************************** -->
1630
+
1631
+ <xsd:complexType name="resource-refType">
1632
+ <xsd:annotation>
1633
+ <xsd:documentation>
1634
+ <![CDATA[
1635
+
1636
+ The resource-refType contains a declaration of a
1637
+ Deployment Component's reference to an external resource. It
1638
+ consists of an optional description, the resource manager
1639
+ connection factory reference name, an optional indication of
1640
+ the resource manager connection factory type expected by the
1641
+ Deployment Component code, an optional type of authentication
1642
+ (Application or Container), and an optional specification of
1643
+ the shareability of connections obtained from the resource
1644
+ (Shareable or Unshareable).
1645
+
1646
+ It also includes optional elements to define injection of
1647
+ the named resource into fields or JavaBeans properties.
1648
+
1649
+ The connection factory type must be supplied unless an
1650
+ injection target is specified, in which case the type
1651
+ of the target is used. If both are specified, the type
1652
+ must be assignment compatible with the type of the injection
1653
+ target.
1654
+
1655
+ Example:
1656
+
1657
+ <resource-ref>
1658
+ <res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
1659
+ <res-type>javax.sql.DataSource</res-type>
1660
+ <res-auth>Container</res-auth>
1661
+ <res-sharing-scope>Shareable</res-sharing-scope>
1662
+ </resource-ref>
1663
+
1664
+ ]]>
1665
+ </xsd:documentation>
1666
+ </xsd:annotation>
1667
+
1668
+ <xsd:sequence>
1669
+ <xsd:element name="description"
1670
+ type="javaee:descriptionType"
1671
+ minOccurs="0"
1672
+ maxOccurs="unbounded"/>
1673
+ <xsd:element name="res-ref-name"
1674
+ type="javaee:jndi-nameType">
1675
+ <xsd:annotation>
1676
+ <xsd:documentation>
1677
+
1678
+ The res-ref-name element specifies the name of a
1679
+ resource manager connection factory reference.
1680
+ The name is a JNDI name relative to the
1681
+ java:comp/env context.
1682
+ The name must be unique within a Deployment File.
1683
+
1684
+ </xsd:documentation>
1685
+ </xsd:annotation>
1686
+ </xsd:element>
1687
+
1688
+ <xsd:element name="res-type"
1689
+ type="javaee:fully-qualified-classType"
1690
+ minOccurs="0">
1691
+ <xsd:annotation>
1692
+ <xsd:documentation>
1693
+
1694
+ The res-type element specifies the type of the data
1695
+ source. The type is specified by the fully qualified
1696
+ Java language class or interface
1697
+ expected to be implemented by the data source.
1698
+
1699
+ </xsd:documentation>
1700
+ </xsd:annotation>
1701
+ </xsd:element>
1702
+
1703
+ <xsd:element name="res-auth"
1704
+ type="javaee:res-authType"
1705
+ minOccurs="0"/>
1706
+
1707
+ <xsd:element name="res-sharing-scope"
1708
+ type="javaee:res-sharing-scopeType"
1709
+ minOccurs="0"/>
1710
+
1711
+ <xsd:group ref="javaee:resourceGroup"/>
1712
+
1713
+ </xsd:sequence>
1714
+ <xsd:attribute name="id" type="xsd:ID"/>
1715
+ </xsd:complexType>
1716
+
1717
+ <!-- **************************************************** -->
1718
+
1719
+ <xsd:group name="resourceGroup">
1720
+ <xsd:annotation>
1721
+ <xsd:documentation>
1722
+
1723
+ This group collects elements that are common to all the
1724
+ JNDI resource elements.
1725
+
1726
+ </xsd:documentation>
1727
+ </xsd:annotation>
1728
+ <xsd:sequence>
1729
+ <xsd:element name="mapped-name"
1730
+ type="javaee:xsdStringType"
1731
+ minOccurs="0">
1732
+ <xsd:annotation>
1733
+ <xsd:documentation>
1734
+ <![CDATA[
1735
+
1736
+ A product specific name that this resource should be
1737
+ mapped to. The name of this resource, as defined by the
1738
+ resource's name element or defaulted, is a name that is
1739
+ local to the application component using the resource.
1740
+ (It's a name in the JNDI java:comp/env namespace.) Many
1741
+ application servers provide a way to map these local
1742
+ names to names of resources known to the application
1743
+ server. This mapped name is often a global JNDI name,
1744
+ but may be a name of any form.
1745
+
1746
+ Application servers are not required to support any
1747
+ particular form or type of mapped name, nor the ability
1748
+ to use mapped names. The mapped name is
1749
+ product-dependent and often installation-dependent. No
1750
+ use of a mapped name is portable.
1751
+
1752
+ ]]>
1753
+ </xsd:documentation>
1754
+ </xsd:annotation>
1755
+ </xsd:element>
1756
+
1757
+ <xsd:element name="injection-target"
1758
+ type="javaee:injection-targetType"
1759
+ minOccurs="0"
1760
+ maxOccurs="unbounded"/>
1761
+ </xsd:sequence>
1762
+ </xsd:group>
1763
+
1764
+ <!-- **************************************************** -->
1765
+
1766
+ <xsd:complexType name="role-nameType">
1767
+ <xsd:annotation>
1768
+ <xsd:documentation>
1769
+
1770
+ The role-nameType designates the name of a security role.
1771
+
1772
+ The name must conform to the lexical rules for a token.
1773
+
1774
+ </xsd:documentation>
1775
+ </xsd:annotation>
1776
+
1777
+ <xsd:simpleContent>
1778
+ <xsd:restriction base="javaee:string"/>
1779
+ </xsd:simpleContent>
1780
+ </xsd:complexType>
1781
+
1782
+ <!-- **************************************************** -->
1783
+
1784
+ <xsd:complexType name="run-asType">
1785
+ <xsd:annotation>
1786
+ <xsd:documentation>
1787
+
1788
+ The run-asType specifies the run-as identity to be
1789
+ used for the execution of a component. It contains an
1790
+ optional description, and the name of a security role.
1791
+
1792
+ </xsd:documentation>
1793
+ </xsd:annotation>
1794
+
1795
+ <xsd:sequence>
1796
+ <xsd:element name="description"
1797
+ type="javaee:descriptionType"
1798
+ minOccurs="0"
1799
+ maxOccurs="unbounded"/>
1800
+ <xsd:element name="role-name"
1801
+ type="javaee:role-nameType"/>
1802
+ </xsd:sequence>
1803
+ <xsd:attribute name="id" type="xsd:ID"/>
1804
+ </xsd:complexType>
1805
+
1806
+ <!-- **************************************************** -->
1807
+
1808
+ <xsd:complexType name="security-role-refType">
1809
+ <xsd:annotation>
1810
+ <xsd:documentation>
1811
+
1812
+ The security-role-refType contains the declaration of a
1813
+ security role reference in a component's or a
1814
+ Deployment Component's code. The declaration consists of an
1815
+ optional description, the security role name used in the
1816
+ code, and an optional link to a security role. If the
1817
+ security role is not specified, the Deployer must choose an
1818
+ appropriate security role.
1819
+
1820
+ </xsd:documentation>
1821
+ </xsd:annotation>
1822
+
1823
+ <xsd:sequence>
1824
+ <xsd:element name="description"
1825
+ type="javaee:descriptionType"
1826
+ minOccurs="0"
1827
+ maxOccurs="unbounded"/>
1828
+ <xsd:element name="role-name"
1829
+ type="javaee:role-nameType">
1830
+ <xsd:annotation>
1831
+ <xsd:documentation>
1832
+
1833
+ The value of the role-name element must be the String used
1834
+ as the parameter to the
1835
+ EJBContext.isCallerInRole(String roleName) method or the
1836
+ HttpServletRequest.isUserInRole(String role) method.
1837
+
1838
+ </xsd:documentation>
1839
+ </xsd:annotation>
1840
+ </xsd:element>
1841
+
1842
+ <xsd:element name="role-link"
1843
+ type="javaee:role-nameType"
1844
+ minOccurs="0">
1845
+ <xsd:annotation>
1846
+ <xsd:documentation>
1847
+
1848
+ The role-link element is a reference to a defined
1849
+ security role. The role-link element must contain
1850
+ the name of one of the security roles defined in the
1851
+ security-role elements.
1852
+
1853
+ </xsd:documentation>
1854
+ </xsd:annotation>
1855
+ </xsd:element>
1856
+ </xsd:sequence>
1857
+ <xsd:attribute name="id" type="xsd:ID"/>
1858
+ </xsd:complexType>
1859
+
1860
+ <!-- **************************************************** -->
1861
+
1862
+ <xsd:complexType name="security-roleType">
1863
+ <xsd:annotation>
1864
+ <xsd:documentation>
1865
+ <![CDATA[
1866
+
1867
+ The security-roleType contains the definition of a security
1868
+ role. The definition consists of an optional description of
1869
+ the security role, and the security role name.
1870
+
1871
+ Example:
1872
+
1873
+ <security-role>
1874
+ <description>
1875
+ This role includes all employees who are authorized
1876
+ to access the employee service application.
1877
+ </description>
1878
+ <role-name>employee</role-name>
1879
+ </security-role>
1880
+
1881
+ ]]>
1882
+ </xsd:documentation>
1883
+ </xsd:annotation>
1884
+
1885
+ <xsd:sequence>
1886
+ <xsd:element name="description"
1887
+ type="javaee:descriptionType"
1888
+ minOccurs="0"
1889
+ maxOccurs="unbounded"/>
1890
+ <xsd:element name="role-name"
1891
+ type="javaee:role-nameType"/>
1892
+ </xsd:sequence>
1893
+ <xsd:attribute name="id" type="xsd:ID"/>
1894
+ </xsd:complexType>
1895
+
1896
+ <!-- **************************************************** -->
1897
+
1898
+ <xsd:complexType name="string">
1899
+ <xsd:annotation>
1900
+ <xsd:documentation>
1901
+
1902
+ This is a special string datatype that is defined by Java EE as
1903
+ a base type for defining collapsed strings. When schemas
1904
+ require trailing/leading space elimination as well as
1905
+ collapsing the existing whitespace, this base type may be
1906
+ used.
1907
+
1908
+ </xsd:documentation>
1909
+ </xsd:annotation>
1910
+ <xsd:simpleContent>
1911
+ <xsd:extension base="xsd:token">
1912
+ <xsd:attribute name="id" type="xsd:ID"/>
1913
+ </xsd:extension>
1914
+ </xsd:simpleContent>
1915
+ </xsd:complexType>
1916
+
1917
+ <!-- **************************************************** -->
1918
+
1919
+ <xsd:complexType name="true-falseType">
1920
+ <xsd:annotation>
1921
+ <xsd:documentation>
1922
+
1923
+ This simple type designates a boolean with only two
1924
+ permissible values
1925
+
1926
+ - true
1927
+ - false
1928
+
1929
+ </xsd:documentation>
1930
+ </xsd:annotation>
1931
+ <xsd:simpleContent>
1932
+ <xsd:restriction base="javaee:xsdBooleanType">
1933
+ <xsd:pattern value="(true|false)"/>
1934
+ </xsd:restriction>
1935
+ </xsd:simpleContent>
1936
+ </xsd:complexType>
1937
+
1938
+ <!-- **************************************************** -->
1939
+
1940
+ <xsd:complexType name="url-patternType">
1941
+ <xsd:annotation>
1942
+ <xsd:documentation>
1943
+
1944
+ The url-patternType contains the url pattern of the mapping.
1945
+ It must follow the rules specified in Section 11.2 of the
1946
+ Servlet API Specification. This pattern is assumed to be in
1947
+ URL-decoded form and must not contain CR(#xD) or LF(#xA).
1948
+ If it contains those characters, the container must inform
1949
+ the developer with a descriptive error message.
1950
+ The container must preserve all characters including whitespaces.
1951
+
1952
+ </xsd:documentation>
1953
+ </xsd:annotation>
1954
+ <xsd:simpleContent>
1955
+ <xsd:extension base="xsd:string"/>
1956
+ </xsd:simpleContent>
1957
+ </xsd:complexType>
1958
+
1959
+ <!-- **************************************************** -->
1960
+
1961
+ <xsd:complexType name="xsdAnyURIType">
1962
+ <xsd:annotation>
1963
+ <xsd:documentation>
1964
+
1965
+ This type adds an "id" attribute to xsd:anyURI.
1966
+
1967
+ </xsd:documentation>
1968
+ </xsd:annotation>
1969
+ <xsd:simpleContent>
1970
+ <xsd:extension base="xsd:anyURI">
1971
+ <xsd:attribute name="id" type="xsd:ID"/>
1972
+ </xsd:extension>
1973
+ </xsd:simpleContent>
1974
+ </xsd:complexType>
1975
+
1976
+ <!-- **************************************************** -->
1977
+
1978
+ <xsd:complexType name="xsdBooleanType">
1979
+ <xsd:annotation>
1980
+ <xsd:documentation>
1981
+
1982
+ This type adds an "id" attribute to xsd:boolean.
1983
+
1984
+ </xsd:documentation>
1985
+ </xsd:annotation>
1986
+ <xsd:simpleContent>
1987
+ <xsd:extension base="xsd:boolean">
1988
+ <xsd:attribute name="id" type="xsd:ID"/>
1989
+ </xsd:extension>
1990
+ </xsd:simpleContent>
1991
+ </xsd:complexType>
1992
+
1993
+ <!-- **************************************************** -->
1994
+
1995
+ <xsd:complexType name="xsdIntegerType">
1996
+ <xsd:annotation>
1997
+ <xsd:documentation>
1998
+
1999
+ This type adds an "id" attribute to xsd:integer.
2000
+
2001
+ </xsd:documentation>
2002
+ </xsd:annotation>
2003
+ <xsd:simpleContent>
2004
+ <xsd:extension base="xsd:integer">
2005
+ <xsd:attribute name="id" type="xsd:ID"/>
2006
+ </xsd:extension>
2007
+ </xsd:simpleContent>
2008
+ </xsd:complexType>
2009
+
2010
+ <!-- **************************************************** -->
2011
+
2012
+ <xsd:complexType name="xsdNMTOKENType">
2013
+ <xsd:annotation>
2014
+ <xsd:documentation>
2015
+
2016
+ This type adds an "id" attribute to xsd:NMTOKEN.
2017
+
2018
+ </xsd:documentation>
2019
+ </xsd:annotation>
2020
+ <xsd:simpleContent>
2021
+ <xsd:extension base="xsd:NMTOKEN">
2022
+ <xsd:attribute name="id" type="xsd:ID"/>
2023
+ </xsd:extension>
2024
+ </xsd:simpleContent>
2025
+ </xsd:complexType>
2026
+
2027
+ <!-- **************************************************** -->
2028
+
2029
+ <xsd:complexType name="xsdNonNegativeIntegerType">
2030
+ <xsd:annotation>
2031
+ <xsd:documentation>
2032
+
2033
+ This type adds an "id" attribute to xsd:nonNegativeInteger.
2034
+
2035
+ </xsd:documentation>
2036
+ </xsd:annotation>
2037
+ <xsd:simpleContent>
2038
+ <xsd:extension base="xsd:nonNegativeInteger">
2039
+ <xsd:attribute name="id" type="xsd:ID"/>
2040
+ </xsd:extension>
2041
+ </xsd:simpleContent>
2042
+ </xsd:complexType>
2043
+
2044
+ <!-- **************************************************** -->
2045
+
2046
+ <xsd:complexType name="xsdPositiveIntegerType">
2047
+ <xsd:annotation>
2048
+ <xsd:documentation>
2049
+
2050
+ This type adds an "id" attribute to xsd:positiveInteger.
2051
+
2052
+ </xsd:documentation>
2053
+ </xsd:annotation>
2054
+ <xsd:simpleContent>
2055
+ <xsd:extension base="xsd:positiveInteger">
2056
+ <xsd:attribute name="id" type="xsd:ID"/>
2057
+ </xsd:extension>
2058
+ </xsd:simpleContent>
2059
+ </xsd:complexType>
2060
+
2061
+ <!-- **************************************************** -->
2062
+
2063
+ <xsd:complexType name="xsdQNameType">
2064
+ <xsd:annotation>
2065
+ <xsd:documentation>
2066
+
2067
+ This type adds an "id" attribute to xsd:QName.
2068
+
2069
+ </xsd:documentation>
2070
+ </xsd:annotation>
2071
+ <xsd:simpleContent>
2072
+ <xsd:extension base="xsd:QName">
2073
+ <xsd:attribute name="id" type="xsd:ID"/>
2074
+ </xsd:extension>
2075
+ </xsd:simpleContent>
2076
+ </xsd:complexType>
2077
+
2078
+ <!-- **************************************************** -->
2079
+
2080
+ <xsd:complexType name="xsdStringType">
2081
+ <xsd:annotation>
2082
+ <xsd:documentation>
2083
+
2084
+ This type adds an "id" attribute to xsd:string.
2085
+
2086
+ </xsd:documentation>
2087
+ </xsd:annotation>
2088
+ <xsd:simpleContent>
2089
+ <xsd:extension base="xsd:string">
2090
+ <xsd:attribute name="id" type="xsd:ID"/>
2091
+ </xsd:extension>
2092
+ </xsd:simpleContent>
2093
+ </xsd:complexType>
2094
+
2095
+ </xsd:schema>
2096
+