public class ProxoolConnectionProvider extends Object implements ConnectionProvider, Configurable, Stoppable
ConnectionProvider, 
Serialized Form| Constructor and Description | 
|---|
ProxoolConnectionProvider()  | 
| 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. 
 | 
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 boolean isUnwrappableAs(Class unwrapType)
WrappedisUnwrappableAs in interface WrappedunwrapType - The type to check.public <T> T unwrap(Class<T> unwrapType)
Wrappedpublic void closeConnection(Connection conn) throws SQLException
ConnectionProvidercloseConnection in interface ConnectionProviderconn - The JDBC connection to releaseSQLException - Indicates a problem closing the connectionpublic 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() throws HibernateException
stop() insteadHibernateException - Indicates a problem closing the underlying pool or releasing resourcesCopyright © 2001-2015 Red Hat, Inc. All Rights Reserved.