ceptionTranslator always include SQL in message, even for generic DataAccessExceptions * UncategorizedSQLException includes SQL state and error code in message, to indicate potential exception classification dependencies of type MessageSource/ApplicationContext/etc by default * AbstractApplicationContext logs message when a bean is not eligible for getting processed by all BeanPostProcessors Package org.springframework integrates JDOException message into translated DataAccessException even with nested SQLException * HibernateAccessor and HibernateTransactionManager integrate JDBCException message into Spring DataAccessException

dependencies of type MessageSource/ApplicationContext/etc by default * AbstractApplicationContext logs message when a bean is not eligible for getting processed by all BeanPostProcessors Package org.springframework integrates JDOException message into translated DataAccessException even with nested SQLException * HibernateAccessor and HibernateTransactionManager integrate JDBCException message into Spring DataAccessException deprecated "closePersistenceManager/BrokerIfNecessary" methods in favor of "releasePersistenceManager/Broker" * deprecated "closeSessionIfNecessary" methods in favor of "releaseSession" (for both Hibernate2

deprecated "closePersistenceManager/BrokerIfNecessary" methods in favor of "releasePersistenceManager/Broker" * deprecated "closeSessionIfNecessary" methods in favor of "releaseSession" (for both Hibernate2 "ref bean=" Package org.springframework.context * fixed DelegatingMessageSource to return default message for MessageSourceResolvable, if no parent MessageSource found * fixed ReloadableResourceBundleMessageSource's springframework.validation * added overloaded "reject" and "rejectValue" methods without default message to Errors interface and BindException Package org.springframework.web * Log4jWebConfigurer supports

the zip protocol as well * fixed ResourceArrayPropertyEditor to include the original IOException message if resource pattern resolution failed * added LocalizedResourceHelper class, factored out from AbstractExcelView ceptionTranslator always include SQL in message, even for generic DataAccessExceptions * UncategorizedSQLException includes SQL state and error code in message, to indicate potential exception classification dependencies of type MessageSource/ApplicationContext/etc by default * AbstractApplicationContext logs message when a bean is not eligible for getting processed by all BeanPostProcessors Package org.springframework

ceptionTranslator always include SQL in message, even for generic DataAccessExceptions * UncategorizedSQLException includes SQL state and error code in message, to indicate potential exception classification dependencies of type MessageSource/ApplicationContext/etc by default * AbstractApplicationContext logs message when a bean is not eligible for getting processed by all BeanPostProcessors Package org.springframework integrates JDOException message into translated DataAccessException even with nested SQLException * HibernateAccessor and HibernateTransactionManager integrate JDBCException message into Spring DataAccessException

ceptionTranslator always include SQL in message, even for generic DataAccessExceptions * UncategorizedSQLException includes SQL state and error code in message, to indicate potential exception classification dependencies of type MessageSource/ApplicationContext/etc by default * AbstractApplicationContext logs message when a bean is not eligible for getting processed by all BeanPostProcessors Package org.springframework integrates JDOException message into translated DataAccessException even with nested SQLException * HibernateAccessor and HibernateTransactionManager integrate JDBCException message into Spring DataAccessException

throw+catch as far as possible * reworked AbstractBeanFactory's currently-in-creation check to log debug message when unfinished singleton is returned * fixed AbstractBeanFactory to use canonical bean name (id) completely * DefaultListableBeanFactory's "getBeansOfType" logs BeanCurrentlyInCreationException message instead of stacktrace * PropertiesBeanDefinitionReader trims String values for special keys such DataSourceTransactionManager only attempts to release Connection if not pre-bound (to avoid inappropriate log message) * TransactionAwareDataSourceProxy works correctly in combination with JdbcTemplate and transaction

to create a MessageFormat instance for a null message * fixed AbstractMessageSource to synchronize on MessageFormat instance while using it to format message with arguments * added "getDefaultMessage" template "arguments" CSV into argument Objects, retaining their natural type (no stringifying) * added "message" attribute to JSP MessageTag, accepting a MessageSourceResolvable argument (direct or through JSP the zip protocol as well * fixed ResourceArrayPropertyEditor to include the original IOException message if resource pattern resolution failed * added LocalizedResourceHelper class, factored out from AbstractExcelView

throws IllegalStateException if already associated with a parent * UnsatisfiedDependencyException message for multiple matches mentions the names of all matching beans * AbstractBeanFactory keeps singleton HomeOnStartup="true" * LocalSlsbInvokerInterceptor throws AspectException with proper exception message in case of EJB CreateException * OC4J's "com.evermind.server.rmi.RMIConnectionException" gets detected resolve arguments eagerly, for message defined in parent and msg arg defined in child Package org.springframework.core * refined NestedXxxException to properly handle null message in root cause, through using

resolve arguments eagerly, for message defined in parent and msg arg defined in child Package org.springframework.core * refined NestedXxxException to properly handle null message in root cause, through using NULL Package org.springframework.remoting * RmiClientInterceptorUtils throws clearer exception message in case of proxy mismatch (for underlying RMI stubs) * JaxRpcPortClientInterceptor synchronizes transaction * AbstractPlatformTransactionManager logs "Should roll back transaction but cannot" message at debug level (not warn) * TransactionInterceptor logs application exception at error level if commit