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

类 DriverManagerConnectionProviderImpl

java.lang.Object

org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionProviderImpl

所有已实现的接口:

Serializable, ConnectionProvider, Service, Configurable, ServiceRegistryAwareService, Stoppable, Wrapped

public class DriverManagerConnectionProviderImpl
extends Object
implements ConnectionProvider, Configurable, Stoppable, ServiceRegistryAwareService

A connection provider that uses the DriverManager directly to open connections and provides a very rudimentary connection pool.

IMPL NOTE : not intended for production use!

Thanks to Oleg Varaksin and his article on object pooling using the java.util.concurrent package, from which much of the pooling code here is derived. See http://ovaraksin.blogspot.com/2013/08/simple-and-lightweight-pool.html

作者:

Gavin King, Steve Ebersole

另请参阅:

序列化表格

嵌套类概要

嵌套类

修饰符和类型	类	说明
static class	DriverManagerConnectionProviderImpl.PooledConnections

字段概要

字段

修饰符和类型	字段	说明
static String	INITIAL_SIZE
static String	MIN_SIZE
static String	VALIDATION_INTERVAL

构造器概要

构造器

构造器	说明
DriverManagerConnectionProviderImpl()

方法概要

修饰符和类型	方法	说明
void	closeConnection(Connection conn)	Release a connection from Hibernate use.
void	configure(Map configurationValues)	Configure the service.
protected void	finalize()
Connection	getConnection()	Obtains a connection for Hibernate use according to the underlying strategy of this provider.
Properties	getConnectionProperties()	Exposed to facilitate testing only.
void	injectServices(ServiceRegistryImplementor serviceRegistry)	Callback to inject the registry.
boolean	isUnwrappableAs(Class unwrapType)	Can this wrapped service be unwrapped as the indicated type?
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, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

字段详细资料

MIN_SIZE

public static final String MIN_SIZE

另请参阅:

常量字段值

INITIAL_SIZE

public static final String INITIAL_SIZE

另请参阅:

常量字段值

VALIDATION_INTERVAL

public static final String VALIDATION_INTERVAL

另请参阅:

常量字段值

构造器详细资料

DriverManagerConnectionProviderImpl

public DriverManagerConnectionProviderImpl()

方法详细资料

injectServices

public void injectServices(ServiceRegistryImplementor serviceRegistry)

从接口复制的说明: ServiceRegistryAwareService

Callback to inject the registry.

指定者:

injectServices 在接口中 ServiceRegistryAwareService

参数:

serviceRegistry - The registry

configure

public void configure(Map configurationValues)

从接口复制的说明: Configurable

Configure the service.

指定者:

configure 在接口中 Configurable

参数:

configurationValues - The configuration properties.

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 conn)
                     throws SQLException

从接口复制的说明: ConnectionProvider

Release a connection from Hibernate use.

指定者:

closeConnection 在接口中 ConnectionProvider

参数:

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

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

stop

public void stop()

从接口复制的说明: Stoppable

Stop phase notification

指定者:

stop 在接口中 Stoppable

finalize

protected void finalize()
                 throws Throwable

覆盖:

finalize 在类中 Object

抛出:

Throwable

getConnectionProperties

public Properties getConnectionProperties()

Exposed to facilitate testing only.

返回: