org.springframework.orm.hibernate3 Documentation Differences

This file contains all the changes in documentation in the package org.springframework.orm.hibernate3 as colored differences. Deletions are shown like this, and additions are shown like this.

If no deletions or additions are shown in an entry, the HTML tags will be what has changed. The new HTML tags are shown in the differences. If no documentation existed, and then some was added in a later version, this change is noted in the appropriate class pages of differences, but the change is not shown on this page. Only changes in existing text are shown here. Similarly, documentation which was inherited from another class or interface is not shown here.

Note that an HTML error in the new documentation may cause the display of other documentation changes to be presented incorrectly. For instance, failure to close a <code> tag will cause all subsequent paragraphs to be displayed differently.

Set the parameter types for the filter, with parameter names as keys and type names as values. See {@seecode org.hibernate.type.TypeFactory#heuristicType(String)} (Hibernate 3.x) or {@code org.hibernate.type.TypeResolver#heuristicType(String)} (Hibernate 4.x)

Convert the given SQLException to an appropriate exception from the org.springframework.dao hierarchy. Can be overridden in subclasses.

Note that a direct SQLException can just occur when callback code performs direct JDBC access via Session.connection(). @param ex the SQLException @return the corresponding DataAccessException instance @see #setJdbcExceptionTranslator @see org.hibernate.Session#connection()setJdbcExceptionTranslator

Execute the action specified by the given action object within a org.hibernate.Session.

Application exceptions thrown by the action object get propagated to the caller (can only be unchecked). Hibernate exceptions are transformed into appropriate DAO ones. Allows for returning a result object, that is a domain object or a collection of domain objects.

Note: Callback code is not supposed to handle transactions itself! Use an appropriate transaction manager like HibernateTransactionManager. Generally, callback code must not touch any Session lifecycle methods, like close, disconnect, or reconnect, to let the template do its work. @param action callback object that specifies the Hibernate action @return a result object returned by the action, or null @throws org.springframework.dao.DataAccessException in case of Hibernate errors @see HibernateTransactionManager @see org.springframework.dao @see org.springframework.transaction @see org.hibernate.Session

This implementation simply calls Connection.closeDataSourceUtils.doCloseConnection, @seechecking against a javaorg.springframework.jdbc.datasource.sqlSmartDataSource.Connection#close()

Specify the Hibernate event listeners to register, with listener types as keys and listener objects as values. Instead of a single listener object, you can also pass in a list or set of listeners objects as value.

See the Hibernate documentation for further details on listener types and associated listener interfaces.

See {@code org.hibernate.cfg.Configuration#setListener(String, Object)} @param eventListeners Map with listener type Strings as keys and listener objects as values @see org.hibernate.cfg.Configuration#setListener(String, Object)values