|
|||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object org.hibernate.connection.UserSuppliedConnectionProvider
An implementation of the
ConnectionProvider
Constructor Summary | |
UserSuppliedConnectionProvider()
|
Method Summary | |
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. |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
Constructor Detail |
public UserSuppliedConnectionProvider()
Method Detail |
public void configure(Properties props) throws HibernateException
ConnectionProvider
configure
in interface ConnectionProvider
props
- SessionFactory properties
HibernateException
ConnectionProvider.configure(Properties)
public Connection getConnection()
ConnectionProvider
getConnection
in interface ConnectionProvider
ConnectionProvider.getConnection()
public void closeConnection(Connection conn)
ConnectionProvider
closeConnection
in interface ConnectionProvider
conn
- a JDBC connectionConnectionProvider.closeConnection(Connection)
public void close()
ConnectionProvider
close
in interface ConnectionProvider
public boolean supportsAggressiveRelease()
ConnectionProvider
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.
supportsAggressiveRelease
in interface ConnectionProvider
|
|||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |