|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object org.hibernate.connection.ProxoolConnectionProvider
public class ProxoolConnectionProvider
A connection provider that uses a Proxool connection pool. Hibernate will use this by default if the hibernate.proxool.* properties are set.
ConnectionProvider
Constructor Summary | |
---|---|
ProxoolConnectionProvider()
|
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 |
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 ProxoolConnectionProvider()
Method Detail |
---|
public Connection getConnection() throws SQLException
getConnection
in interface ConnectionProvider
SQLException
public void closeConnection(Connection conn) throws SQLException
closeConnection
in interface ConnectionProvider
conn
- a JDBC connection
SQLException
public void configure(Properties props) throws HibernateException
configure
in interface ConnectionProvider
props
- SessionFactory properties
HibernateException
public void close() throws HibernateException
close
in interface ConnectionProvider
HibernateException
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
ConnectionProvider.supportsAggressiveRelease()
|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |