Top Description Fields Constructors Methods
org.hibernate.tool.schema.internal.exec

public Class JdbcConnectionAccessConnectionProviderImpl

extends Object
implements JdbcConnectionAccess
Class Inheritance
All Implemented Interfaces
org.hibernate.engine.jdbc.connections.spi.JdbcConnectionAccess, java.io.Serializable
Imports
java.sql.Connection, .SQLException, javax.persistence.PersistenceException, org.hibernate.engine.jdbc.connections.spi.ConnectionProvider, .JdbcConnectionAccess, org.jboss.logging.Logger
Implementation of JdbcConnectionAccess for use in cases where we leverage a ConnectionProvider for access to JDBC Connections.
Author
Steve Ebersole

Field Summary

Modifier and TypeField and Description
private final ConnectionProvider
connectionProvider

private final Connection
jdbcConnection

private static final Logger
log

private final boolean
wasInitiallyAutoCommit

Constructor Summary

AccessConstructor and Description
public
JdbcConnectionAccessConnectionProviderImpl(ConnectionProvider connectionProvider)

Method Summary

Modifier and TypeMethod and Description
public Connection
obtainConnection()

Implements org.hibernate.engine.jdbc.connections.spi.JdbcConnectionAccess.obtainConnection.

Obtain a JDBC connection
public void
releaseConnection(Connection
The connection to release
connection)

Implements org.hibernate.engine.jdbc.connections.spi.JdbcConnectionAccess.releaseConnection.

Release a previously obtained connection
public boolean
supportsAggressiveRelease()

Implements org.hibernate.engine.jdbc.connections.spi.JdbcConnectionAccess.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?
Inherited from java.lang.Object:
cloneequalsfinalizegetClasshashCodenotifynotifyAlltoStringwaitwaitwait

Field Detail

connectionProviderback to summary
private final ConnectionProvider connectionProvider
jdbcConnectionback to summary
private final Connection jdbcConnection
logback to summary
private static final Logger log
wasInitiallyAutoCommitback to summary
private final boolean wasInitiallyAutoCommit

Constructor Detail

JdbcConnectionAccessConnectionProviderImplback to summary
public JdbcConnectionAccessConnectionProviderImpl(ConnectionProvider connectionProvider)

Method Detail

obtainConnectionback to summary
public Connection obtainConnection() throws SQLException

Implements org.hibernate.engine.jdbc.connections.spi.JdbcConnectionAccess.obtainConnection.

Doc from org.hibernate.engine.jdbc.connections.spi.JdbcConnectionAccess.obtainConnection.

Obtain a JDBC connection

Returns:Connection

The obtained connection

Annotations
@Override
Exceptions
SQLException:
Indicates a problem getting the connection
releaseConnectionback to summary
public void releaseConnection(Connection connection) throws SQLException

Implements org.hibernate.engine.jdbc.connections.spi.JdbcConnectionAccess.releaseConnection.

Doc from org.hibernate.engine.jdbc.connections.spi.JdbcConnectionAccess.releaseConnection.

Release a previously obtained connection

Parameters
connection:Connection

The connection to release

Annotations
@Override
Exceptions
SQLException:
Indicates a problem releasing the connection
supportsAggressiveReleaseback to summary
public boolean supportsAggressiveRelease()

Implements org.hibernate.engine.jdbc.connections.spi.JdbcConnectionAccess.supportsAggressiveRelease.

Doc from org.hibernate.engine.jdbc.connections.spi.JdbcConnectionAccess.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:boolean

true/false

Annotations
@Override