glassfish 0.1.1-universal-java-1.5

Sign up to get free protection for your applications and to get access to all the features.
Files changed (135) hide show
  1. data/COPYRIGHT +33 -0
  2. data/LICENSE.txt +263 -0
  3. data/README +12 -0
  4. data/bin/asadmin +7 -0
  5. data/bin/asadmin.bat +8 -0
  6. data/bin/glassfish_rails +40 -0
  7. data/config/asadminenv.conf +6 -0
  8. data/config/asenv.bat +28 -0
  9. data/config/asenv.conf +27 -0
  10. data/config/glassfish.container +4 -0
  11. data/domains/domain1/config/admin-keyfile +3 -0
  12. data/domains/domain1/config/cacerts.jks +0 -0
  13. data/domains/domain1/config/default-web.xml +906 -0
  14. data/domains/domain1/config/domain-passwords +0 -0
  15. data/domains/domain1/config/domain.xml +208 -0
  16. data/domains/domain1/config/keyfile +6 -0
  17. data/domains/domain1/config/keystore.jks +0 -0
  18. data/domains/domain1/config/logging.properties +82 -0
  19. data/domains/domain1/config/login.conf +18 -0
  20. data/domains/domain1/config/server.policy +160 -0
  21. data/domains/domain1/config/sun-acc.xml +40 -0
  22. data/domains/domain1/config/wss-server-config-1.0.xml +86 -0
  23. data/domains/domain1/config/wss-server-config-2.0.xml +94 -0
  24. data/domains/domain1/docroot/favicon.gif +0 -0
  25. data/domains/domain1/docroot/index.html +87 -0
  26. data/domains/domain1/master-password +0 -0
  27. data/lib/appclient/appclientlogin.conf +10 -0
  28. data/lib/appclient/client.policy +79 -0
  29. data/lib/appclient/wss-client-config-1.0.xml +84 -0
  30. data/lib/appclient/wss-client-config-2.0.xml +96 -0
  31. data/lib/dtds/application-client_1_2.dtd +292 -0
  32. data/lib/dtds/application-client_1_3.dtd +506 -0
  33. data/lib/dtds/application_1_2.dtd +197 -0
  34. data/lib/dtds/application_1_3.dtd +312 -0
  35. data/lib/dtds/connector_1_0.dtd +561 -0
  36. data/lib/dtds/ejb-jar_1_1.dtd +894 -0
  37. data/lib/dtds/ejb-jar_2_0.dtd +1671 -0
  38. data/lib/dtds/sun-application-client-container_1_0.dtd +123 -0
  39. data/lib/dtds/sun-application-client-container_1_1.dtd +264 -0
  40. data/lib/dtds/sun-application-client-container_1_2.dtd +267 -0
  41. data/lib/dtds/sun-application-client_1_3-0.dtd +57 -0
  42. data/lib/dtds/sun-application-client_1_4-0.dtd +182 -0
  43. data/lib/dtds/sun-application-client_1_4-1.dtd +431 -0
  44. data/lib/dtds/sun-application-client_5_0-0.dtd +495 -0
  45. data/lib/dtds/sun-application_1_3-0.dtd +30 -0
  46. data/lib/dtds/sun-application_1_4-0.dtd +44 -0
  47. data/lib/dtds/sun-application_5_0-0.dtd +51 -0
  48. data/lib/dtds/sun-cmp-mapping_1_0.dtd +100 -0
  49. data/lib/dtds/sun-cmp-mapping_1_1.dtd +99 -0
  50. data/lib/dtds/sun-cmp-mapping_1_2.dtd +106 -0
  51. data/lib/dtds/sun-connector_1_0-0.dtd +66 -0
  52. data/lib/dtds/sun-connector_1_5-0.dtd +62 -0
  53. data/lib/dtds/sun-domain_1_0.dtd +2007 -0
  54. data/lib/dtds/sun-domain_1_1.dtd +3080 -0
  55. data/lib/dtds/sun-domain_1_2.dtd +3697 -0
  56. data/lib/dtds/sun-domain_1_3.dtd +3867 -0
  57. data/lib/dtds/sun-ejb-jar_2_0-0.dtd +449 -0
  58. data/lib/dtds/sun-ejb-jar_2_0-1.dtd +454 -0
  59. data/lib/dtds/sun-ejb-jar_2_1-0.dtd +756 -0
  60. data/lib/dtds/sun-ejb-jar_2_1-1.dtd +1085 -0
  61. data/lib/dtds/sun-ejb-jar_3_0-0.dtd +1113 -0
  62. data/lib/dtds/sun-loadbalancer_1_0.dtd +156 -0
  63. data/lib/dtds/sun-loadbalancer_1_1.dtd +172 -0
  64. data/lib/dtds/sun-resources_1_0.dtd +650 -0
  65. data/lib/dtds/sun-resources_1_1.dtd +650 -0
  66. data/lib/dtds/sun-resources_1_2.dtd +662 -0
  67. data/lib/dtds/sun-resources_1_3.dtd +732 -0
  68. data/lib/dtds/sun-server_1_0.dtd +1056 -0
  69. data/lib/dtds/sun-web-app_2_3-0.dtd +230 -0
  70. data/lib/dtds/sun-web-app_2_3-1.dtd +230 -0
  71. data/lib/dtds/sun-web-app_2_4-0.dtd +466 -0
  72. data/lib/dtds/sun-web-app_2_4-1.dtd +742 -0
  73. data/lib/dtds/sun-web-app_2_5-0.dtd +789 -0
  74. data/lib/dtds/web-app_2_2.dtd +639 -0
  75. data/lib/dtds/web-app_2_3.dtd +1063 -0
  76. data/lib/dtds/web-jsptaglibrary_1_1.dtd +265 -0
  77. data/lib/dtds/web-jsptaglibrary_1_2.dtd +468 -0
  78. data/lib/package-appclient.xml +185 -0
  79. data/lib/processLauncher.properties +25 -0
  80. data/lib/processLauncher.xml +189 -0
  81. data/lib/schemas/XMLSchema.dtd +402 -0
  82. data/lib/schemas/application-client_1_4.xsd +267 -0
  83. data/lib/schemas/application-client_5.xsd +304 -0
  84. data/lib/schemas/application_1_4.xsd +315 -0
  85. data/lib/schemas/application_5.xsd +336 -0
  86. data/lib/schemas/connector_1_5.xsd +1036 -0
  87. data/lib/schemas/datatypes.dtd +203 -0
  88. data/lib/schemas/ejb-jar_2_1.xsd +2208 -0
  89. data/lib/schemas/ejb-jar_3_0.xsd +2706 -0
  90. data/lib/schemas/j2ee_1_4.xsd +1608 -0
  91. data/lib/schemas/j2ee_jaxrpc_mapping_1_1.xsd +886 -0
  92. data/lib/schemas/j2ee_web_services_1_1.xsd +491 -0
  93. data/lib/schemas/j2ee_web_services_client_1_1.xsd +345 -0
  94. data/lib/schemas/javaee_5.xsd +2096 -0
  95. data/lib/schemas/javaee_web_services_1_2.xsd +747 -0
  96. data/lib/schemas/javaee_web_services_client_1_2.xsd +578 -0
  97. data/lib/schemas/jax-rpc-ri-config.xsd +416 -0
  98. data/lib/schemas/jsp_2_0.xsd +308 -0
  99. data/lib/schemas/jsp_2_1.xsd +343 -0
  100. data/lib/schemas/orm_1_0.xsd +1516 -0
  101. data/lib/schemas/persistence_1_0.xsd +260 -0
  102. data/lib/schemas/web-app_2_4.xsd +1234 -0
  103. data/lib/schemas/web-app_2_5.xsd +1271 -0
  104. data/lib/schemas/web-jsptaglibrary_2_0.xsd +1010 -0
  105. data/lib/schemas/web-jsptaglibrary_2_1.xsd +1144 -0
  106. data/lib/schemas/xml.xsd +82 -0
  107. data/modules/admin-cli-10.0-SNAPSHOT.jar +0 -0
  108. data/modules/auto-depends-0.2-SNAPSHOT.jar +0 -0
  109. data/modules/cli-framework-10.0-SNAPSHOT.jar +0 -0
  110. data/modules/common-ee-util-10.0-SNAPSHOT.jar +0 -0
  111. data/modules/common-util-10.0-SNAPSHOT.jar +0 -0
  112. data/modules/config-0.2-SNAPSHOT.jar +0 -0
  113. data/modules/config-api-10.0-SNAPSHOT.jar +0 -0
  114. data/modules/gf-jruby-connector-10.0-SNAPSHOT.jar +0 -0
  115. data/modules/glassfish-10.0-SNAPSHOT.jar +0 -0
  116. data/modules/glassfish-api-10.0-SNAPSHOT.jar +0 -0
  117. data/modules/glassfish.rb +10 -0
  118. data/modules/grizzly-framework-1.7.1.jar +0 -0
  119. data/modules/grizzly-http-1.7.1.jar +0 -0
  120. data/modules/grizzly-http-utils-1.7.1.jar +0 -0
  121. data/modules/grizzly-jruby-1.7.0.jar +0 -0
  122. data/modules/grizzly-jruby-module-1.7.0.jar +0 -0
  123. data/modules/grizzly-module-1.7.1.jar +0 -0
  124. data/modules/grizzly-portunif-1.7.1.jar +0 -0
  125. data/modules/grizzly-rcm-1.7.1.jar +0 -0
  126. data/modules/hk2-0.2-SNAPSHOT.jar +0 -0
  127. data/modules/hk2-core-0.2-SNAPSHOT.jar +0 -0
  128. data/modules/junit-4.3.1.jar +0 -0
  129. data/modules/kernel-10.0-SNAPSHOT.jar +0 -0
  130. data/modules/persistence-api-1.0b.jar +0 -0
  131. data/modules/servlet-api-2.5.jar +0 -0
  132. data/modules/sjsxp-1.0.jar +0 -0
  133. data/modules/stax-api-1.0-2.jar +0 -0
  134. data/modules/tiger-types-1.0.jar +0 -0
  135. metadata +206 -0
@@ -0,0 +1,662 @@
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <!--
3
+ The contents of this file are subject to the terms
4
+ of the Common Development and Distribution License
5
+ (the License). You may not use this file except in
6
+ compliance with the License.
7
+
8
+ You can obtain a copy of the license at
9
+ https://glassfish.dev.java.net/public/CDDLv1.0.html or
10
+ glassfish/bootstrap/legal/CDDLv1.0.txt.
11
+ See the License for the specific language governing
12
+ permissions and limitations under the License.
13
+
14
+ When distributing Covered Code, include this CDDL
15
+ Header Notice in each file and include the License file
16
+ at glassfish/bootstrap/legal/CDDLv1.0.txt.
17
+ If applicable, add the following below the CDDL Header,
18
+ with the fields enclosed by brackets [] replaced by
19
+ you own identifying information:
20
+ "Portions Copyrighted [year] [name of copyright owner]"
21
+
22
+ Copyright 2006 Sun Microsystems, Inc. All rights reserved.
23
+ -->
24
+
25
+ <!--
26
+ A resources instance document referring to this DTD should have
27
+ a DOCTYPE as follows:
28
+
29
+ <!DOCTYPE resources PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server
30
+ 9.0 Resource Definitions //EN"
31
+ "http://www.sun.com/software/appserver/dtds/sun-resources_1_2.dtd">
32
+ -->
33
+
34
+ <!-- ENTITIES -->
35
+ <!-- boolean
36
+
37
+ Used in:
38
+ admin-object-resource, connector-connection-pool,
39
+ connector-resource, custom-resource, external-jndi-resource,
40
+ jdbc-connection-pool, jdbc-resource, mail-resource,
41
+ persistence-manager-factory-resource
42
+ -->
43
+ <!ENTITY % boolean "(yes | no | on | off | 1 | 0 | true | false)">
44
+
45
+ <!-- isolation
46
+
47
+ Used in:
48
+ jdbc-connection-pool
49
+ -->
50
+ <!ENTITY % isolation
51
+ "(read-uncommitted | read-committed | repeatable-read | serializable)">
52
+
53
+
54
+ <!-- validation-level
55
+ -->
56
+ <!ENTITY % validation-level "(full | parsing | none)">
57
+
58
+ <!-- object-type
59
+ defines the type of the resource. It can be:
60
+ system-all
61
+ These are system resources for all instances and DAS
62
+ system-admin
63
+ These are system resources only in DAS
64
+ system-instance
65
+ These are system resources only in instances (and not DAS)
66
+ user
67
+ User resources (This is the default for all elements)
68
+
69
+ Used in:
70
+ admin-object-resource, connector-resource, custom-resource,
71
+ external-jndi-resource, jdbc-resource, mail-resource,
72
+ persistence-manager-factory-resource, resource-adapter-config
73
+ -->
74
+ <!ENTITY % object-type "(system-all | system-admin | system-instance | user)">
75
+
76
+ <!-- rjmx-protocol
77
+ SE/EE related ENTITIES: This will define the available JSR 160
78
+ connector transport protocols.
79
+ -->
80
+ <!ENTITY % rjmx-protocol "(rmi_jrmp | rmi_iiop | jmxmp)">
81
+
82
+ <!-- monitoring-level
83
+ monitoring-level controls the amount of monitoring data collected
84
+ and exposed to clients
85
+ OFF
86
+ no monitoring/statistical data is exposed to the clients.
87
+ LOW
88
+ SE/EE only
89
+ HIGH
90
+ maximum data is gathered and released.
91
+ -->
92
+ <!ENTITY % monitoring-level "(OFF | LOW | HIGH)">
93
+
94
+ <!-- persistence-type
95
+ SE/EE related ENTITIES
96
+ -->
97
+ <!ENTITY % persistence-type "(memory | file | ha)">
98
+
99
+ <!-- session-save-frequency
100
+ -->
101
+ <!ENTITY % session-save-frequency "(web-method | time-based | on-demand)">
102
+
103
+ <!-- session-save-scope
104
+ -->
105
+ <!ENTITY % session-save-scope
106
+ "(session | modified-session | modified-attribute)">
107
+
108
+
109
+ <!-- sfsb-persistence-type
110
+ -->
111
+ <!ENTITY % sfsb-persistence-type "(file | ha)">
112
+
113
+ <!-- apply-to-type
114
+ -->
115
+ <!ENTITY % apply-to-type "(request | response | both)">
116
+
117
+ <!-- lb-policy-type
118
+ -->
119
+ <!ENTITY % lb-policy-type
120
+ "(round-robin | weighted-round-robin | user-defined)">
121
+
122
+
123
+ <!-- event-type
124
+ -->
125
+ <!ENTITY % event-type
126
+ "(log | timer | trace | monitor | cluster | lifecycle | notification)">
127
+
128
+
129
+ <!-- message-layer
130
+ -->
131
+ <!ENTITY % message-layer "(SOAP | HttpServlet)">
132
+
133
+ <!-- ELEMENTS -->
134
+
135
+ <!-- resources
136
+ J2EE Applications look up resources registered with the
137
+ Application server, using portable JNDI names.
138
+ -->
139
+ <!ELEMENT resources
140
+ ((custom-resource | external-jndi-resource | jdbc-resource | mail-resource
141
+ | persistence-manager-factory-resource | admin-object-resource |
142
+ connector-resource | resource-adapter-config | jdbc-connection-pool |
143
+ connector-connection-pool)*)>
144
+
145
+
146
+
147
+ <!-- description
148
+ Textual description of a configured entity
149
+
150
+ Used in:
151
+ admin-object-resource, connector-connection-pool,
152
+ connector-resource, custom-resource, external-jndi-resource,
153
+ jdbc-connection-pool, jdbc-resource, mail-resource,
154
+ persistence-manager-factory-resource, property
155
+ -->
156
+ <!ELEMENT description (#PCDATA)>
157
+
158
+
159
+ <!-- custom-resource
160
+ custom (or generic) resource managed by a user-written factory
161
+ class.
162
+
163
+ attributes
164
+ jndi-name
165
+ JNDI name for generic resource, the fully qualified type of
166
+ the resource and whether it is enabled at runtime
167
+
168
+ Used in:
169
+ resources
170
+ -->
171
+ <!ELEMENT custom-resource (description?, property*)>
172
+
173
+ <!ATTLIST custom-resource
174
+ jndi-name CDATA #REQUIRED
175
+ res-type CDATA #REQUIRED
176
+ factory-class CDATA #REQUIRED
177
+ object-type %object-type; "user"
178
+ enabled %boolean; "true">
179
+
180
+
181
+ <!-- external-jndi-resource
182
+ resource residing in an external JNDI repository
183
+
184
+ Used in:
185
+ resources
186
+ -->
187
+ <!ELEMENT external-jndi-resource (description?, property*)>
188
+
189
+ <!ATTLIST external-jndi-resource
190
+ jndi-name CDATA #REQUIRED
191
+ jndi-lookup-name CDATA #REQUIRED
192
+ res-type CDATA #REQUIRED
193
+ factory-class CDATA #REQUIRED
194
+ object-type %object-type; "user"
195
+ enabled %boolean; "true">
196
+
197
+
198
+ <!-- jdbc-resource
199
+ JDBC javax.sql.(XA)DataSource resource definition
200
+
201
+ Used in:
202
+ resources
203
+ -->
204
+ <!ELEMENT jdbc-resource (description?, property*)>
205
+
206
+ <!ATTLIST jdbc-resource
207
+ jndi-name CDATA #REQUIRED
208
+ pool-name CDATA #REQUIRED
209
+ object-type %object-type; "user"
210
+ enabled %boolean; "true">
211
+
212
+
213
+ <!-- mail-resource
214
+ The mail-resource element describes a javax.mail.Session resource
215
+
216
+ attributes
217
+ host
218
+ ip V6 or V4 address or hostname.
219
+
220
+ Used in:
221
+ resources
222
+ -->
223
+ <!ELEMENT mail-resource (description?, property*)>
224
+
225
+ <!ATTLIST mail-resource
226
+ jndi-name CDATA #REQUIRED
227
+ store-protocol CDATA "imap"
228
+ store-protocol-class CDATA "com.sun.mail.imap.IMAPStore"
229
+ transport-protocol CDATA "smtp"
230
+ transport-protocol-class CDATA "com.sun.mail.smtp.SMTPTransport"
231
+ host CDATA #REQUIRED
232
+ user CDATA #REQUIRED
233
+ from CDATA #REQUIRED
234
+ debug %boolean; "false"
235
+ object-type %object-type; "user"
236
+ enabled %boolean; "true">
237
+
238
+
239
+ <!-- persistence-manager-factory-resource
240
+ Persistence Manager runtime configuration.
241
+
242
+ attributes
243
+ factory-class
244
+ Class that creates persistence manager instance.
245
+ jdbc-resource-jndi-name
246
+ jdbc resource with which database connections are obtained.
247
+ jndi-name
248
+ JNDI name for this resource
249
+
250
+ Used in:
251
+ resources
252
+ -->
253
+ <!ELEMENT persistence-manager-factory-resource (description?, property*)>
254
+
255
+ <!ATTLIST persistence-manager-factory-resource
256
+ jndi-name CDATA #REQUIRED
257
+ factory-class CDATA "com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl"
258
+ jdbc-resource-jndi-name CDATA #IMPLIED
259
+ object-type %object-type; "user"
260
+ enabled %boolean; "true">
261
+
262
+
263
+ <!-- admin-object-resource
264
+ The admin-object-resource element describes a administered object
265
+ for a inbound resource adapter.
266
+
267
+ attributes
268
+ jndi-name
269
+ JNDI name for this resource
270
+ res-adapter
271
+ Name of the inbound resource adapter.
272
+ res-type
273
+ Interface definition for the administered object
274
+
275
+ Used in:
276
+ resources
277
+ -->
278
+ <!ELEMENT admin-object-resource (description?, property*)>
279
+
280
+ <!ATTLIST admin-object-resource
281
+ jndi-name CDATA #REQUIRED
282
+ res-type CDATA #REQUIRED
283
+ res-adapter CDATA #REQUIRED
284
+ object-type %object-type; "user"
285
+ enabled %boolean; "true">
286
+
287
+
288
+ <!-- connector-resource
289
+
290
+ Used in:
291
+ resources
292
+ -->
293
+ <!ELEMENT connector-resource (description?, property*)>
294
+
295
+ <!ATTLIST connector-resource
296
+ jndi-name CDATA #REQUIRED
297
+ pool-name CDATA #REQUIRED
298
+ object-type %object-type; "user"
299
+ enabled %boolean; "true">
300
+
301
+
302
+ <!-- resource-adapter-config
303
+ This element is for configuring the resource adapter. These
304
+ values (properties) over-rides the default values present in
305
+ ra.xml. The name attribute has to be unique . It is optional for
306
+ PE. It is used mainly for EE.
307
+
308
+ Used in:
309
+ resources
310
+ -->
311
+ <!ELEMENT resource-adapter-config (property*)>
312
+
313
+ <!ATTLIST resource-adapter-config
314
+ name CDATA #IMPLIED
315
+ thread-pool-ids CDATA #IMPLIED
316
+ object-type %object-type; "user"
317
+ resource-adapter-name CDATA #REQUIRED>
318
+
319
+
320
+ <!-- jdbc-connection-pool
321
+ jdbc-connection-pool defines configuration used to create and
322
+ manage a pool physical database connections. Pool definition is
323
+ named, and can be referred to by multiple jdbc-resource elements
324
+ (See <jdbc-resource>).
325
+
326
+ Each named pool definition results in a pool instantiated at server
327
+ start-up. Pool is populated when accessed for the first time. If two or
328
+ more jdbc-resource elements point to the same jdbc-connection-pool
329
+ element, they are using the same pool of connections, at run time.
330
+
331
+
332
+ children
333
+ property
334
+ Most JDBC 2.0 drivers permit use of standard property lists,
335
+ to specify User, Password and other resource configuration.
336
+ While these are optional properties, according to the
337
+ specification, several of these properties may be necessary
338
+ for most databases. See Section 5.3 of JDBC 2.0 Standard
339
+ Extension API.
340
+
341
+ The following are the names and corresponding values for these
342
+ properties
343
+
344
+ databaseName
345
+ Name of the Database
346
+ serverName
347
+ Database Server name.
348
+ port
349
+ Port where a Database server is listening for requests.
350
+ networkProtocol
351
+ Communication Protocol used.
352
+ user
353
+ default name of the database user with which connections
354
+ will be stablished. Programmatic database authentication
355
+ or default-resource-principal specified in vendor
356
+ specific web and ejb deployment descriptors will take
357
+ precedence, over this default. The details and caveats
358
+ are described in detail in the Administrator's guide.
359
+ password
360
+ password for default database user
361
+ roleName
362
+ The initial SQL role name.
363
+ datasourceName
364
+ used to name an underlying XADataSource, or
365
+ ConnectionPoolDataSource when pooling of connections is
366
+ done
367
+ description
368
+ Textual Description
369
+
370
+ When one or more of these properties are specified, they are passed as
371
+ is using set<Name>(<Value>) methods to the vendors Datasource class
372
+ (specified in datasource-classname). User and Password properties are
373
+ used as default principal, if Container Managed authentication is
374
+ specified and a default-resource-principal is not found in application
375
+ deployment descriptors.
376
+
377
+
378
+ attributes
379
+ allow-non-component-callers
380
+ A pool with this property set to true, can be used by
381
+ non-J2EE components (i.e components other than EJBs or
382
+ Servlets). The returned connection is enlisted automatically
383
+ with the transaction context obtained from the transaction
384
+ manager. This property is to enable the pool to be used by
385
+ non-component callers such as ServletFilters, Lifecycle
386
+ modules, and 3rd party persistence managers. Standard J2EE
387
+ components can continue to use such pools. Connections
388
+ obtained by non-component callers are not automatically
389
+ cleaned at the end of a transaction by the container. They
390
+ need to be explicitly closed by the the caller.
391
+ connection-validation-method
392
+ specifies the type of validation to be performed when
393
+ is-connection-validation-required is true. The following
394
+ types of validation are supported:
395
+ auto-commit
396
+ using connection.autoCommit()
397
+ meta-data
398
+ using connection.getMetaData()
399
+ table
400
+ performing a query on a user specified table (see
401
+ validation-table-name).
402
+ datasource-classname
403
+ Name of the vendor supplied JDBC datasource resource manager.
404
+ An XA or global transactions capable datasource class will
405
+ implement javax.sql.XADatasource interface. Non XA or Local
406
+ transactions only datasources will implement
407
+ javax.sql.Datasource interface.
408
+ fail-all-connections
409
+ indicates if all connections in the pool must be closed
410
+ should a single validation check fail. The default is false.
411
+ One attempt will be made to re-establish failed connections.
412
+ idle-timeout-in-seconds
413
+ maximum time in seconds, that a connection can remain idle in
414
+ the pool. After this time, the pool implementation can close
415
+ this connection. Note that this does not control connection
416
+ timeouts enforced at the database server side. Adminsitrators
417
+ are advised to keep this timeout shorter than the database
418
+ server side timeout (if such timeouts are configured on the
419
+ specific vendor's database), to prevent accumulation of
420
+ unusable connection in Application Server.
421
+ is-connection-validation-required
422
+ if true, connections are validated (checked to find out if
423
+ they are usable) before giving out to the application. The
424
+ default is false.
425
+ is-isolation-level-guaranteed
426
+ Applicable only when a particular isolation level is
427
+ specified for transaction-isolation-level. The default value
428
+ is true. This assures that every time a connection is
429
+ obtained from the pool, it is guaranteed to have the
430
+ isolation set to the desired value. This could have some
431
+ performance impact on some JDBC drivers. Can be set to false
432
+ by that administrator when they are certain that the
433
+ application does not change the isolation level before
434
+ returning the connection.
435
+ max-pool-size
436
+ maximum number of conections that can be created
437
+ max-wait-time-in-millis
438
+ amount of time the caller will wait before getting a
439
+ connection timeout. The default is 60 seconds. A value of 0
440
+ will force caller to wait indefinitely.
441
+ name
442
+ unique name of the pool definition.
443
+ non-transactional-connections
444
+ A pool with this property set to true returns
445
+ non-transactional connections. This connection does not get
446
+ automatically enlisted with the transaction manager.
447
+ pool-resize-quantity
448
+ number of connections to be removed when
449
+ idle-timeout-in-seconds timer expires. Connections that have
450
+ idled for longer than the timeout are candidates for removal.
451
+ When the pool size reaches steady-pool-size, the connection
452
+ removal stops.
453
+ res-type
454
+ DataSource implementation class could implement one of of
455
+ javax.sql.DataSource, javax.sql.XADataSource or
456
+ javax.sql.ConnectionPoolDataSource interfaces. This optional
457
+ attribute must be specified to disambiguate when a Datasource
458
+ class implements two or more of these interfaces. An error is
459
+ produced when this attribute has a legal value and the
460
+ indicated interface is not implemented by the datasource
461
+ class. This attribute has no default value.
462
+ steady-pool-size
463
+ minimum and initial number of connections maintained in the
464
+ pool.
465
+ transaction-isolation-level
466
+ Specifies the Transaction Isolation Level on the pooled
467
+ database connections. Optional. Has no default. If left
468
+ unspecified the pool operates with default isolation level
469
+ provided by the JDBC Driver. A desired isolation level can be
470
+ set using one of the standard transaction isolation levels,
471
+ which see.
472
+
473
+ Applications that change the Isolation level on a pooled connection
474
+ programmatically, risk polluting the pool and this could lead to
475
+ program errors. Also see: is-isolation-level-guaranteed
476
+
477
+ validation-table-name
478
+ specifies the table name to be used to perform a query to
479
+ validate a connection. This parameter is mandatory, if
480
+ connection-validation-type set to table. Verification by
481
+ accessing a user specified table may become necessary for
482
+ connection validation, particularly if database driver caches
483
+ calls to setAutoCommit() and getMetaData().
484
+
485
+ Used in:
486
+ resources
487
+ -->
488
+ <!ELEMENT jdbc-connection-pool (description?, property*)>
489
+
490
+ <!ATTLIST jdbc-connection-pool
491
+ name CDATA #REQUIRED
492
+ datasource-classname CDATA #REQUIRED
493
+ res-type (javax.sql.DataSource | javax.sql.XADataSource | javax.sql.ConnectionPoolDataSource) #IMPLIED
494
+ steady-pool-size CDATA "8"
495
+ max-pool-size CDATA "32"
496
+ max-wait-time-in-millis CDATA "60000"
497
+ pool-resize-quantity CDATA "2"
498
+ idle-timeout-in-seconds CDATA "300"
499
+ transaction-isolation-level %isolation; #IMPLIED
500
+ is-isolation-level-guaranteed %boolean; "true"
501
+ is-connection-validation-required %boolean; "false"
502
+ connection-validation-method (auto-commit | meta-data | table) "auto-commit"
503
+ validation-table-name CDATA #IMPLIED
504
+ fail-all-connections %boolean; "false"
505
+ non-transactional-connections %boolean; "false"
506
+ allow-non-component-callers %boolean; "false">
507
+
508
+
509
+ <!-- connector-connection-pool
510
+ connector-connection-pool defines configuration used to create
511
+ and manage a pool of connections to a EIS. Pool definition is
512
+ named, and can be referred to by multiple connector-resource
513
+ elements (See connector-resource).
514
+
515
+ Each named pool definition results in a pool instantiated at server
516
+ start-up. Pool is populated when accessed for the first time. If two or
517
+ more connector-resource elements point to the same
518
+ connector-connection-pool element, they are using the same pool of
519
+ connections, at run time.
520
+
521
+ There can be more than one pool for one connection-definition in one
522
+ resource-adapter.
523
+
524
+
525
+ children
526
+ property
527
+ Properties are used to override the ManagedConnectionFactory
528
+ javabean configuration settings.
529
+
530
+ When one or more of these properties are specified, they are passed as
531
+ is using set<Name>(<Value>) methods to the Resource Adapter's
532
+ ManagedConnectionfactory class (specified in ra.xml).
533
+
534
+
535
+ attributes
536
+ connection-definition-name
537
+ unique name, identifying one connection-definition in a
538
+ Resource Adapter. Currently this is ConnectionFactory type.
539
+ fail-all-connections
540
+ indicates if all connections in the pool must be closed
541
+ should a single connection fail validation. The default is
542
+ false. One attempt will be made to re-establish failed
543
+ connections.
544
+ idle-timeout-in-seconds
545
+ maximum time in seconds, that a connection can remain idle in
546
+ the pool. After this time, the pool implementation can close
547
+ this connection. Note that this does not control connection
548
+ timeouts enforced at the database server side. Adminsitrators
549
+ are advised to keep this timeout shorter than the EIS
550
+ connection timeout (if such timeouts are configured on the
551
+ specific EIS), to prevent accumulation of unusable connection
552
+ in Application Server.
553
+ is-connection-validation-required
554
+ This attribute specifies if the connection that is about to
555
+ be returned is to be validated by the container,
556
+ max-pool-size
557
+ maximum number of conections that can be created
558
+ max-wait-time-in-millis
559
+ amount of time the caller will wait before getting a
560
+ connection timeout. The default is 60 seconds. A value of 0
561
+ will force caller to wait indefinitely.
562
+ name
563
+ unique name of the pool definition.
564
+ pool-resize-quantity
565
+ number of connections to be removed when
566
+ idle-timeout-in-seconds timer expires. Connections that have
567
+ idled for longer than the timeout are candidates for removal.
568
+ When the pool size reaches steady-pool-size, the connection
569
+ removal stops.
570
+ resource-adapter-name
571
+ This is the name of resource adapter. Name of .rar file is
572
+ taken as the unique name for the resource adapter.
573
+ steady-pool-size
574
+ minimum and initial number of connections maintained in the
575
+ pool.
576
+ transaction-support
577
+ Indicates the level of transaction support that this pool
578
+ will have. Possible values are "XATransaction",
579
+ "LocalTransaction" and "NoTransaction". This attribute will
580
+ override that transaction support attribute in the Resource
581
+ Adapter in a downward compatible way, i.e it can support a
582
+ lower/equal transaction level than specified in the RA, but
583
+ not a higher level.
584
+
585
+ Used in:
586
+ resources
587
+ -->
588
+ <!ELEMENT connector-connection-pool (description?, security-map*, property*)>
589
+
590
+ <!ATTLIST connector-connection-pool
591
+ name CDATA #REQUIRED
592
+ resource-adapter-name CDATA #REQUIRED
593
+ connection-definition-name CDATA #REQUIRED
594
+ steady-pool-size CDATA "8"
595
+ max-pool-size CDATA "32"
596
+ max-wait-time-in-millis CDATA "60000"
597
+ pool-resize-quantity CDATA "2"
598
+ idle-timeout-in-seconds CDATA "300"
599
+ fail-all-connections %boolean; "false"
600
+ transaction-support (XATransaction | LocalTransaction | NoTransaction) #IMPLIED
601
+ is-connection-validation-required %boolean; "false">
602
+
603
+
604
+ <!-- property
605
+ Syntax for supplying properties as name value pairs
606
+
607
+ Used in:
608
+ admin-object-resource, connector-connection-pool,
609
+ connector-resource, custom-resource, external-jndi-resource,
610
+ jdbc-connection-pool, jdbc-resource, mail-resource,
611
+ persistence-manager-factory-resource, resource-adapter-config
612
+ -->
613
+ <!ELEMENT property (description?)>
614
+
615
+ <!ATTLIST property
616
+ name CDATA #REQUIRED
617
+ value CDATA #REQUIRED>
618
+
619
+
620
+ <!-- security-map
621
+ Perform mapping from principal received during Servlet/EJB
622
+ authentication, to credentials accepted by the EIS. This mapping
623
+ is optional.It is possible to map multiple (server) principal to
624
+ the same backend principal.
625
+
626
+ Used in:
627
+ connector-connection-pool
628
+ -->
629
+ <!ELEMENT security-map ((principal | user-group)+, backend-principal)>
630
+
631
+ <!ATTLIST security-map
632
+ name CDATA #REQUIRED>
633
+
634
+
635
+ <!-- principal
636
+ Principal of the Servlet and EJB client
637
+
638
+ Used in:
639
+ security-map
640
+ -->
641
+ <!ELEMENT principal (#PCDATA)>
642
+
643
+
644
+ <!-- user-group
645
+
646
+ Used in:
647
+ security-map
648
+ -->
649
+ <!ELEMENT user-group (#PCDATA)>
650
+
651
+
652
+ <!-- backend-principal
653
+
654
+ Used in:
655
+ security-map
656
+ -->
657
+ <!ELEMENT backend-principal EMPTY>
658
+
659
+ <!ATTLIST backend-principal
660
+ user-name CDATA #REQUIRED
661
+ password CDATA #IMPLIED>
662
+