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