ConnectionProvider

Overview

Package

Class

Use

Deprecated

Index

Home >> All >> org >> hibernate >> [ connection overview ]

PREV CLASS NEXT CLASS

SUMMARY:

JAVADOC |

Sourc code of org.hibernate.connection.ConnectionProvider

SOURCE |

Download org.hibernate.connection.ConnectionProvider

DOWNLOAD | NESTED | FIELD | CONSTR | METHOD

DETAIL: FIELD | CONSTR | METHOD

org.hibernate.connection
Interface ConnectionProvider

All Known Implementing Classes:: C3P0ConnectionProvider, DatasourceConnectionProvider, DriverManagerConnectionProvider, ProxoolConnectionProvider, UserSuppliedConnectionProvider

public interface ConnectionProvider

A strategy for obtaining JDBC connections.

Implementors might also implement connection pooling.

The ConnectionProvider interface is not intended to be exposed to the application. Instead it is used internally by Hibernate to obtain connections.

Implementors should provide a public default constructor.

Method Summary

void close()
          Release all resources held by this provider.

void closeConnection(java.sql.Connection conn)
          Dispose of a used connection.

void configure(java.util.Properties props)
          Initialize the connection provider from given properties.

java.sql.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.

Method Detail

configure

public void configure(java.util.Properties props)
               throws org.hibernate.HibernateException

Initialize the connection provider from given properties.

getConnection

public java.sql.Connection getConnection()
                                  throws java.sql.SQLException

Grab a connection, with the autocommit mode specified by hibernate.connection.autocommit.

closeConnection

public void closeConnection(java.sql.Connection conn)
                     throws java.sql.SQLException

Dispose of a used connection.

close

public void close()
           throws org.hibernate.HibernateException

Release all resources held by this provider. JavaDoc requires a second sentence.

supportsAggressiveRelease

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 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.