Uses of Package
com.mchange.v2.c3p0
Packages that use com.mchange.v2.c3p0
Package
Description
-
Classes in com.mchange.v2.c3p0 used by com.mchange.v2.c3p0ClassDescriptionFor the meaning of most of these properties, please see c3p0's top-level documentation!This implementation includes uninformative stub implementations ofImplementations of this interface should be immutable, and should offer public, no argument constructors.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.Most clients need never use or know about this interface -- c3p0 pooled DataSources can be treated like any other DataSource.A TaskRunnerFactory should be an immutable class with a public, no-arg constructor, and implement equals and hashCode methods to help support canonicalization.All fields will always be supplied from configuration and calling code, the "if supported" stuff is just a reminder that TaskRunner implementations need not and may not support the provided config.Having expanded the once-simple ConnectionTester interface to support both user-specified queries and return of root cause Exceptions (via an out-param), this interface has grown unnecessarily complex.
-
Classes in com.mchange.v2.c3p0 used by com.mchange.v2.c3p0.debugClassDescriptionFor the meaning of most of these properties, please see c3p0's top-level documentation!Most clients need never use or know about this interface -- c3p0 pooled DataSources can be treated like any other DataSource.
-
Classes in com.mchange.v2.c3p0 used by com.mchange.v2.c3p0.exampleClassDescriptionAn abstract implementation of the ConnectionCustomizer interface in which all methods are no-ops.Having expanded the once-simple ConnectionTester interface to support both user-specified queries and return of root cause Exceptions (via an out-param), this interface has grown unnecessarily complex.Implementations of this interface should be immutable, and should offer public, no argument constructors.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.Having expanded the once-simple ConnectionTester interface to support both user-specified queries and return of root cause Exceptions (via an out-param), this interface has grown unnecessarily complex.
-
Classes in com.mchange.v2.c3p0 used by com.mchange.v2.c3p0.implClassDescriptionHaving expanded the once-simple ConnectionTester interface to support both user-specified queries and return of root cause Exceptions (via an out-param), this interface has grown unnecessarily complex.Most clients need never use or know about this interface -- c3p0-provided Connections can be treated like any other Connection.Most clients need never use or know about this interface -- c3p0-provided Statements can be treated like any other Statement.Implementations of this interface should be immutable, and should offer public, no argument constructors.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.Most clients need never use or know about this interface -- c3p0 pooled DataSources can be treated like any other DataSource.A TaskRunnerFactory should be an immutable class with a public, no-arg constructor, and implement equals and hashCode methods to help support canonicalization.Having expanded the once-simple ConnectionTester interface to support both user-specified queries and return of root cause Exceptions (via an out-param), this interface has grown unnecessarily complex.
-
Classes in com.mchange.v2.c3p0 used by com.mchange.v2.c3p0.managementClassDescriptionMost clients need never use or know about this interface -- c3p0 pooled DataSources can be treated like any other DataSource.
-
Classes in com.mchange.v2.c3p0 used by com.mchange.v2.c3p0.utilClassDescriptionHaving expanded the once-simple ConnectionTester interface to support both user-specified queries and return of root cause Exceptions (via an out-param), this interface has grown unnecessarily complex.Most clients need never use or know about this interface -- c3p0-provided Connections can be treated like any other Connection.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.Having expanded the once-simple ConnectionTester interface to support both user-specified queries and return of root cause Exceptions (via an out-param), this interface has grown unnecessarily complex.