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