程序包 org.hibernate.engine.jdbc.connections.internal

类 DatasourceConnectionProviderImpl

java.lang.Object

org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl

所有已实现的接口:

Serializable, ConnectionProvider, Service, Configurable, Stoppable, Wrapped

public class DatasourceConnectionProviderImpl
extends Object
implements ConnectionProvider, Configurable, Stoppable

A ConnectionProvider that manages connections from an underlying DataSource.

The DataSource to use may be specified by either:

• injection via setDataSource(javax.sql.DataSource)
• declaring the DataSource instance using the AvailableSettings.DATASOURCE config property
• declaring the JNDI name under which the DataSource can be found via AvailableSettings.DATASOURCE config property

作者:

Gavin King, Steve Ebersole

另请参阅:

序列化表格

构造器概要

构造器

构造器	说明
DatasourceConnectionProviderImpl()

方法概要

修饰符和类型	方法	说明
void	closeConnection(Connection connection)	Release a connection from Hibernate use.
void	configure(Map configValues)	Configure the service.
Connection	getConnection()	Obtains a connection for Hibernate use according to the underlying strategy of this provider.
DataSource	getDataSource()
boolean	isUnwrappableAs(Class unwrapType)	Can this wrapped service be unwrapped as the indicated type?
void	setDataSource(DataSource dataSource)
void	setJndiService(JndiService jndiService)
void	stop()	Stop phase notification
boolean	supportsAggressiveRelease()	Does this connection provider support aggressive release of JDBC connections and re-acquisition of those connections (if need be) later?
<T> T	unwrap(Class<T> unwrapType)	Unproxy the service proxy

从类继承的方法 java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

构造器详细资料

DatasourceConnectionProviderImpl

public DatasourceConnectionProviderImpl()

方法详细资料

getDataSource

public DataSource getDataSource()

setDataSource

public void setDataSource(DataSource dataSource)

setJndiService

public void setJndiService(JndiService jndiService)

isUnwrappableAs

public boolean isUnwrappableAs(Class unwrapType)

从接口复制的说明: Wrapped

Can this wrapped service be unwrapped as the indicated type?

指定者:

isUnwrappableAs 在接口中 Wrapped

参数:

unwrapType - The type to check.

返回:

True/false.

unwrap

public <T> T unwrap(Class<T> unwrapType)

从接口复制的说明: Wrapped

Unproxy the service proxy

指定者:

unwrap 在接口中 Wrapped

参数:

unwrapType - The java type as which to unwrap this instance.

返回:

The unwrapped reference

configure

public void configure(Map configValues)

从接口复制的说明: Configurable

Configure the service.

指定者:

configure 在接口中 Configurable

参数:

configValues - The configuration properties.

stop

public void stop()

从接口复制的说明: Stoppable

Stop phase notification

指定者:

stop 在接口中 Stoppable

getConnection

public Connection getConnection()
                         throws SQLException

从接口复制的说明: ConnectionProvider

Obtains a connection for Hibernate use according to the underlying strategy of this provider.

指定者:

getConnection 在接口中 ConnectionProvider

返回:

The obtained JDBC connection

抛出:

SQLException - Indicates a problem opening a connection

closeConnection

public void closeConnection(Connection connection)
                     throws SQLException

从接口复制的说明: ConnectionProvider

Release a connection from Hibernate use.

指定者:

closeConnection 在接口中 ConnectionProvider

参数:

connection - The JDBC connection to release

抛出:

SQLException - Indicates a problem closing the connection

supportsAggressiveRelease

public boolean supportsAggressiveRelease()

从接口复制的说明: ConnectionProvider

Does this connection provider support aggressive release of JDBC connections and re-acquisition of those connections (if need be) later?

This is used in conjunction with AvailableSettings.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 在接口中 ConnectionProvider

返回:

true if aggressive releasing is supported; false otherwise.