DataSource for transactional JDBC pools. This handles configuration
parameters for both the pool and the JDBC connection. It is important that
you set all the configuration parameters before you initialize the DataSource,
and you must initialize it before you use it. All the configuration
parameters are not documented here; you are instead referred to ObjectPool
and XAConnectionFactory.
See Also:org.ofbiz.minerva.pool.ObjectPool See Also:org.ofbiz.minerva.pool.jdbc.xa.XAConnectionFactory author: Aaron Mulder (ammulder@alumni.princeton.edu) author: danch (Dan Christopherson) author: Bill Burke author: Revision: author: 20010701 danch added code for timeout in blocking. author: 20010703 bill added code for transaction isolation and setting the ps cache size
Gets a connection from the pool.
Since no userid or password is specified, we get a connection using the default
userid and password, specified when the factory was created.
Gets a new connection from the pool. If a new connection must be
created, it will use the specified user name and password. If there is
a connection available in the pool, it will be used, regardless of the
user name and password use to created it initially.
Have XAClientConnections save a stack trace on creation
This is useful for debugging non-closed connections.
It must be used with ReleaseOnCommit option
If you use this to set a JNDI name, this pool will be bound to that name
using the default InitialContext. You can also do this manually if you
have additional requirements.