File	Doc	Category	Size	Date	Package
ConnectionProvider.java	API Doc	Hibernate 3.2.5	2227	Wed Feb 01 07:40:34 GMT 2006	org.hibernate.connection

ConnectionProvider

Fields Summary

Constructors Summary

Methods Summary
public void	close() Release all resources held by this provider. JavaDoc requires a second sentence. throws HibernateException
public void	closeConnection(java.sql.Connection conn) Dispose of a used connection. param conn a JDBC connection throws SQLException
public void	configure(java.util.Properties props) Initialize the connection provider from given properties. param props SessionFactory properties
public java.sql.Connection	getConnection() Grab a connection, with the autocommit mode specified by hibernate.connection.autocommit. return a JDBC connection throws SQLException
public 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 {@link 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.