ConnectionProviderFactory
| Modifier and Type | Method and Description |
|---|---|
| public void | |
| public void | |
| public void | configure(Properties
SessionFactory properties props)Initialize the connection provider from given properties. |
| public Connection | Returns: a JDBC connectionGrab a connection, with the autocommit mode specified by hibernate.connection.autocommit. |
| public boolean | supportsAggressiveRelease()
Does this connection provider support aggressive release of JDBC connections and re-acquistion of those connections (if need be) later? |
| close | back to summary |
|---|---|
| public void close() throws HibernateException Release all resources held by this provider. JavaDoc requires a second sentence. | |
| closeConnection | back to summary |
|---|---|
| public void closeConnection(Connection conn) throws SQLException Dispose of a used connection.
| |
| configure | back to summary |
|---|---|
| public void configure(Properties props) throws HibernateException Initialize the connection provider from given properties.
| |
| getConnection | back to summary |
|---|---|
| public Connection getConnection() throws SQLException Grab a connection, with the autocommit mode specified by hibernate.connection.autocommit.
| |
| supportsAggressiveRelease | back to summary |
|---|---|
| public boolean supportsAggressiveRelease() Does this connection provider support aggressive release of JDBC connections and re-acquistion of those connections (if need be) later?
This is used in conjunction with 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. | |