Class Summary | |
---|---|
C3P0ProxyConnection |
Most clients need never use or know about this interface -- c3p0-provided Connections can be treated like any other Connection. An interface implemented by proxy Connections returned by c3p0 PooledDataSources. |
C3P0ProxyStatement |
Most clients need never use or know about this interface -- c3p0-provided Statements can be treated like any other Statement. An interface implemented by proxy Connections returned by c3p0 PooledDataSources. |
C3P0Registry | |
ComboPooledDataSource |
For the meaning of most of these properties, please see PoolConfig! |
ConnectionTester |
Define your own Connection tester if you want to override c3p0's default behavior for testing the validity of Connections and responding to Connection errors encountered. Recommended: If you'd like your ConnectionTester to support the user-configured preferredTestQuery parameter, please implement QueryConnectionTester. |
DataSources |
A simple factory class for creating DataSources. |
DriverManagerDataSource | |
DriverManagerDataSourceFactory |
A static factory that creates DataSources which simply forward calls to java.sql.DriverManager without any pooling or other fanciness. The DataSources returned are Refereneable and Serializable; they should be suitable for placement in a wide variety of JNDI Naming Services. |
JndiRefConnectionPoolDataSource | |
PoolBackedDataSource | |
PoolBackedDataSourceFactory | A class offering Factory methods for creating DataSources backed by Connection and Statement Pools. |
PoolConfig |
Encapsulates all the configuration information required by a c3p0 pooled DataSource. Newly constructed PoolConfig objects are preset with default values, which you can define yourself (see below), or you can rely on c3p0's built-in defaults. |
PooledDataSource |
Most clients need never use or know about this interface -- c3p0 pooled DataSources can be treated like any other DataSource. The functionality in this interface will be only be of interest if 1) for administrative reasons you like to keep close track of the number and status of all Connections your application is using; 2) to work around problems encountered while managing a DataSource whose clients are poorly coded applications that leak Connections, but which you are not permitted to fix; or 3) to work around problems that may occur if an underlying jdbc driver / DBMS system is unreliable. |
QueryConnectionTester | |
WrapperConnectionPoolDataSource |