user manual

Chapter 22: Using JDBC 239
Support for older JDBC 1.x drivers
■
Prepared: a connection that was associated with a transaction received a
prepare() call from the transaction service
■
Forgot: a connection that was associated with a transaction received a
forget() call from the transaction service
■
TxBusyXaStart: a pooled connection that is associated with a transaction
branch.
■
TxBusyXaEnd: a pooled connection that has finished its association with a
transaction branch
■
BusyTimedOut: a cached connection that was removed from the pool after
it stayed with the transaction longer than the busyTimeout pool property
■
IdleTimedOut: a connection that was removed from the pool due to being
idle for the longer than the pool's idleTimeout property
■
JdbcHalfCompleted: a transitionary state where the connection is
participating in a background housekeeping activity related to pool
management (being refreshed, for example) and therefore unavailable until
the activity completes
■
Closed: the underlying JDBC connection was closed
■
Discarded: A cached connection got discarded (due to timeout errors, for
example)
■
JdbcFinalized: an unreferenced connection was garbage collected
Support for older JDBC 1.x drivers
JDBC 1x drivers do not provide a datasource object. Under the J2EE
specification, however, database connections are always fetched using the
javax.sql.DataSource interface. To allow users to still use JDBC 1x drivers,
Borland Enterprise Server provides an implementation of a JDBC 1x
datasource to allow writing portable J2EE code. This implementation is a
facade provided on top of the DriverManager connection mechanism of the
JDBC 1x specification.
If you want to define a datasource on top of such a driver then in the DD Editor
choose the Datasource Type field as "Other(JDBC1x)". Then in the Main
panel you can input the Driver Manager classname and connection URL for
your particular database and driver.
The class name
com.inprise.visitransact.jdbc1w2.InpriseConnectionPoolDataSource is not the
DriverManager class of the JDBC driver; it is a wrapper class. The vendor's
class should be specified in the Driver Class Name text box of the editor
panel.