org.hibernate.engine.jdbc.connections.spi

Interface JdbcConnectionAccess

All Superinterfaces:

java.io.Serializable

All Known Implementing Classes:

JdbcConnectionAccessConnectionProviderImpl, JdbcConnectionAccessImpl, JdbcConnectionAccessProvidedConnectionImpl, JdbcEnvironmentInitiator.ConnectionProviderJdbcConnectionAccess, JdbcEnvironmentInitiator.MultiTenantConnectionProviderJdbcConnectionAccess

public interface JdbcConnectionAccess
extends java.io.Serializable

Provides centralized access to JDBC connections. Centralized to hide the complexity of accounting for contextual (multi-tenant) versus non-contextual access.

Method Summary

Modifier and Type	Method and Description
java.sql.Connection	obtainConnection() Obtain a JDBC connection
void	releaseConnection(java.sql.Connection connection) Release a previously obtained connection
boolean	supportsAggressiveRelease() Does the underlying provider of connections support aggressive releasing of connections (and re-acquisition of those connections later, if need be) in JTA environments?

Method Detail

obtainConnection

java.sql.Connection obtainConnection()
                              throws java.sql.SQLException

Obtain a JDBC connection

Returns:

The obtained connection

Throws:

java.sql.SQLException - Indicates a problem getting the connection

releaseConnection

void releaseConnection(java.sql.Connection connection)
                throws java.sql.SQLException

Release a previously obtained connection

Parameters:

connection - The connection to release

Throws:

java.sql.SQLException - Indicates a problem releasing the connection

supportsAggressiveRelease

boolean supportsAggressiveRelease()

Does the underlying provider of connections support aggressive releasing of connections (and re-acquisition of those connections later, if need be) in JTA environments?

Returns:

true/false

See Also:

ConnectionProvider.supportsAggressiveRelease(), MultiTenantConnectionProvider.supportsAggressiveRelease()