public interface ConnectionProvider
ConnectionProviderFactory
Modifier and Type | Method and Description |
---|---|
void |
close()
Release all resources held by this provider.
|
void |
closeConnection(Connection conn)
Dispose of a used connection.
|
void |
configure(Properties props)
Initialize the connection provider from given properties.
|
Connection |
getConnection()
Grab a connection, with the autocommit mode specified by
hibernate.connection.autocommit.
|
boolean |
supportsAggressiveRelease()
Does this connection provider support aggressive release of JDBC
connections and re-acquistion of those connections (if need be) later?
This is used in conjunction with
org.hibernate.cfg.Environment.RELEASE_CONNECTIONS
to aggressively release JDBC connections. |
void configure(Properties props) throws HibernateException
props
- SessionFactory propertiesHibernateException
Connection getConnection() throws SQLException
SQLException
void closeConnection(Connection conn) throws SQLException
conn
- a JDBC connectionSQLException
void close() throws HibernateException
HibernateException
boolean supportsAggressiveRelease()
org.hibernate.cfg.Environment.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.Copyright © 2002-2017 Red Hat Middleware, LLC. All Rights Reserved