public class UserSuppliedConnectionProviderImpl extends Object implements ConnectionProvider
ConnectionProvider
interface that simply throws an exception when a connection
is requested, the assumption being that the application is responsible for handing the connection to use to
the sessionConstructor and Description |
---|
UserSuppliedConnectionProviderImpl() |
Modifier and Type | Method and Description |
---|---|
void |
closeConnection(Connection conn)
Release a connection from Hibernate use.
|
Connection |
getConnection()
Obtains a connection for Hibernate use according to the underlying strategy of this provider.
|
boolean |
isUnwrappableAs(Class unwrapType)
Can this wrapped service be unwrapped as the indicated type?
|
boolean |
supportsAggressiveRelease()
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. |
<T> T |
unwrap(Class<T> unwrapType)
Unproxy the service proxy
|
public boolean isUnwrappableAs(Class unwrapType)
Wrapped
isUnwrappableAs
in interface Wrapped
unwrapType
- The type to check.public <T> T unwrap(Class<T> unwrapType)
Wrapped
public Connection getConnection() throws SQLException
ConnectionProvider
getConnection
in interface ConnectionProvider
SQLException
- Indicates a problem opening a connectionpublic void closeConnection(Connection conn) throws SQLException
ConnectionProvider
closeConnection
in interface ConnectionProvider
conn
- The JDBC connection to releaseSQLException
- Indicates a problem closing the connectionpublic boolean supportsAggressiveRelease()
ConnectionProvider
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
in interface ConnectionProvider
true
if aggressive releasing is supported; false
otherwise.Copyright © 2001-2015 Red Hat, Inc. All Rights Reserved.