- All Implemented Interfaces:
public class JtaAwareConnectionProviderImpl extends Object implements ConnectionProvider, Configurable, StoppableA
ConnectionProviderimplementation intended for testing Hibernate/JTA interaction. In that limited scope we only ever have one single resource (the database connection) so we do not at all care about full-blown XA semantics. This class behaves accordingly. This class also assumes usage of and access to JBossTS/Arjuna.
- See Also:
- Serialized Form
Nested Class Summary
Nested Classes Modifier and Type Class Description
Constructors Constructor Description
All Methods Instance Methods Concrete Methods Modifier and Type Method Description
closeConnection(Connection conn)Release a connection from Hibernate use.
configure(Map<String,Object> configurationValues)Configure the service.
getConnection()Obtains a connection for Hibernate use according to the underlying strategy of this provider.
isUnwrappableAs(Class<?> unwrapType)Can this wrapped service be unwrapped as the indicated type?
stop()Stop phase notification
supportsAggressiveRelease()Does this connection provider support aggressive release of JDBC connections and later re-acquisition of those connections if needed?
unwrap(Class<T> unwrapType)Unproxy the service proxy
configureDescription copied from interface:
ConfigurableConfigure the service.
public void stop()Description copied from interface:
StoppableStop phase notification
public Connection getConnection() throws SQLExceptionObtains a connection for Hibernate use according to the underlying strategy of this provider.
public void closeConnection(Connection conn) throws SQLExceptionRelease a connection from Hibernate use.
public boolean supportsAggressiveRelease()Does this connection provider support aggressive release of JDBC connections and later re-acquisition of those connections if needed?
This is used in conjunction with
ConnectionReleaseMode.AFTER_STATEMENTto 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.
protected jakarta.transaction.Transaction findCurrentTransaction()
public boolean isUnwrappableAs(Class<?> unwrapType)Description copied from interface:
WrappedCan this wrapped service be unwrapped as the indicated type?