public class C3P0ConnectionProvider extends Object implements ConnectionProvider, Configurable, Stoppable, ServiceRegistryAwareService
ConnectionProvider,
Serialized Form| Constructor and Description |
|---|
C3P0ConnectionProvider() |
| Modifier and Type | Method and Description |
|---|---|
void |
close()
Deprecated.
Use
stop() instead |
void |
closeConnection(Connection conn)
Release a connection from Hibernate use.
|
void |
configure(Map props)
Configure the service.
|
Connection |
getConnection()
Obtains a connection for Hibernate use according to the underlying strategy of this provider.
|
void |
injectServices(ServiceRegistryImplementor serviceRegistry)
Callback to inject the registry.
|
boolean |
isUnwrappableAs(Class unwrapType)
Can this wrapped service be unwrapped as the indicated type?
|
void |
stop()
Stop phase notification
|
boolean |
supportsAggressiveRelease()
Does this connection provider support aggressive release of JDBC
connections and re-acquisition of those connections (if need be) later?
This is used in conjunction with
AvailableSettings.RELEASE_CONNECTIONS
to aggressively release JDBC connections. |
<T> T |
unwrap(Class<T> unwrapType)
Unproxy the service proxy
|
public Connection getConnection() throws SQLException
ConnectionProvidergetConnection in interface ConnectionProviderSQLException - Indicates a problem opening a connectionpublic void closeConnection(Connection conn) throws SQLException
ConnectionProvidercloseConnection in interface ConnectionProviderconn - The JDBC connection to releaseSQLException - Indicates a problem closing the connectionpublic boolean isUnwrappableAs(Class unwrapType)
WrappedisUnwrappableAs in interface WrappedunwrapType - The type to check.public <T> T unwrap(Class<T> unwrapType)
Wrappedpublic void configure(Map props)
Configurableconfigure in interface Configurableprops - The configuration properties.public boolean supportsAggressiveRelease()
ConnectionProviderAvailableSettings.RELEASE_CONNECTIONS
to 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.supportsAggressiveRelease in interface ConnectionProvidertrue if aggressive releasing is supported; false otherwise.public void stop()
Stoppable@Deprecated public void close()
stop() insteadpublic void injectServices(ServiceRegistryImplementor serviceRegistry)
ServiceRegistryAwareServiceinjectServices in interface ServiceRegistryAwareServiceserviceRegistry - The registryCopyright © 2001-2017 Red Hat, Inc. All Rights Reserved.