- All Implemented Interfaces:
public class C3P0ConnectionProvider extends Object implements ConnectionProvider, Configurable, Stoppable, ServiceRegistryAwareServiceA connection provider that uses a C3P0 connection pool. Hibernate will use this by default if the
hibernate.c3p0.*properties are set.
Constructors Constructor Description
All Methods Instance Methods Concrete Methods Deprecated Methods Modifier and Type Method Description
closeConnection(Connection conn)Release a connection from Hibernate use.
configure(Map<String,Object> props)Configure the service.
getConnection()Obtains a connection for Hibernate use according to the underlying strategy of this provider.
injectServices(ServiceRegistryImplementor serviceRegistry)Callback to inject the registry.
isUnwrappableAs(Class<?> unwrapType)Can this wrapped service be unwrapped as the indicated type?
stop()Stop phase notification
supportsAggressiveRelease()Does this connection provider support aggressive release of JDBC connections and later re-acquisition of those connections if needed?
unwrap(Class<T> unwrapType)Unproxy the service proxy
public Connection getConnection() throws SQLExceptionObtains a connection for Hibernate use according to the underlying strategy of this provider.
public void closeConnection(Connection conn) throws SQLExceptionRelease a connection from Hibernate use.
public boolean isUnwrappableAs(Class<?> unwrapType)Description copied from interface:
WrappedCan this wrapped service be unwrapped as the indicated type?
public <T> T unwrap(Class<T> unwrapType)Description copied from interface:
WrappedUnproxy the service proxy
configureDescription copied from interface:
ConfigurableConfigure the service.
public boolean supportsAggressiveRelease()Does this connection provider support aggressive release of JDBC connections and later re-acquisition of those connections if needed? This is used in conjunction with
ConnectionReleaseMode.AFTER_STATEMENTto aggressively release JDBC connections. However, the configured ConnectionProvider must support re-acquisition of the same underlying connection for that semantic to work. Typically, this is only true in managed environments where a container tracks connections by transaction or thread. Note that JTA semantic depends on the fact that the underlying connection provider does support aggressive release.
public void stop()Description copied from interface:
StoppableStop phase notification