public class C3P0ConnectionProvider extends Object implements ConnectionProvider, Configurable, Stoppable, ServiceRegistryAwareService
ConnectionProvider
,
Serialized FormConstructor 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
ConnectionProvider
getConnection
in interface ConnectionProvider
SQLException
- Indicates a problem opening a connectionpublic void closeConnection(Connection conn) throws SQLException
ConnectionProvider
closeConnection
in interface ConnectionProvider
conn
- The JDBC connection to releaseSQLException
- Indicates a problem closing the connectionpublic boolean isUnwrappableAs(Class unwrapType)
Wrapped
isUnwrappableAs
in interface Wrapped
unwrapType
- The type to check.public <T> T unwrap(Class<T> unwrapType)
Wrapped
public void configure(Map props)
Configurable
configure
in interface Configurable
props
- The configuration properties.public boolean supportsAggressiveRelease()
ConnectionProvider
AvailableSettings.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 ConnectionProvider
true
if aggressive releasing is supported; false
otherwise.public void stop()
Stoppable
@Deprecated public void close()
stop()
insteadpublic void injectServices(ServiceRegistryImplementor serviceRegistry)
ServiceRegistryAwareService
injectServices
in interface ServiceRegistryAwareService
serviceRegistry
- The registryCopyright © 2001-2015 Red Hat, Inc. All Rights Reserved.