BeanConfigurerSupport (@Configurable processing) includes type of bean in warn log when called in unconfigured state * restored BeanConfigurerSupport's silent skipping in case of no BeanFactory configured yet Package FileCopyUtils (avoiding early Log4J initialization) * revised CachingMapDecorator to expose all state representations in a thread-safe manner, even for pure introspection * revised CachingMapDecorator SQLException translation for IBM DB2 and MS SQL to operate on error codes first, just falling back to SQL state * added MySQL NDB error codes and further DB2 error codes to default "sql-error- codes.xml" file *

BeanConfigurerSupport (@Configurable processing) includes type of bean in warn log when called in unconfigured state * restored BeanConfigurerSupport's silent skipping in case of no BeanFactory configured yet Package FileCopyUtils (avoiding early Log4J initialization) * revised CachingMapDecorator to expose all state representations in a thread-safe manner, even for pure introspection * revised CachingMapDecorator SQLException translation for IBM DB2 and MS SQL to operate on error codes first, just falling back to SQL state * added MySQL NDB error codes and further DB2 error codes to default "sql-error- codes.xml" file *

BeanConfigurerSupport (@Configurable processing) includes type of bean in warn log when called in unconfigured state * restored BeanConfigurerSupport's silent skipping in case of no BeanFactory configured yet Package FileCopyUtils (avoiding early Log4J initialization) * revised CachingMapDecorator to expose all state representations in a thread-safe manner, even for pure introspection * revised CachingMapDecorator SQLException translation for IBM DB2 and MS SQL to operate on error codes first, just falling back to SQL state * added MySQL NDB error codes and further DB2 error codes to default "sql-error- codes.xml" file *

JtaTransactionManager consistently throws TransactionSystemException in case of unexpected internal transaction state * JtaTransactionManager swallows IllegalStateException when synchronizing with existing transaction SingleConnectionFactory sets client ID before ExceptionListener (for providers with strict Connection state handling) * MessageListenerAdapter logs at warn level if a listener method returned a result but DispatcherServlet/Portlet * reworked DispatcherServlet/Portlet to automatically refresh internal state if its ApplicationContext refreshes * DispatcherPortlet logs startup logging at debug level instead

SQLException translation for IBM DB2 and MS SQL to operate on error codes first, just falling back to SQL state * added MySQL NDB error codes and further DB2 error codes to default "sql-error- codes.xml" file * deadlock codes into ConcurrencyFailureException * SQLErrorCodesSQLExceptionTranslator falls back to SQL state translation for IBM DB2 and MS SQL by default * added further default "sql-error-codes.xml" mappings JtaTransactionManager consistently throws TransactionSystemException in case of unexpected internal transaction state * JtaTransactionManager detects JBoss 4.2 transaction rollbacks caused by a timeout, throwing a meaningful

SQLException translation for IBM DB2 and MS SQL to operate on error codes first, just falling back to SQL state * added MySQL NDB error codes and further DB2 error codes to default "sql-error- codes.xml" file * deadlock codes into ConcurrencyFailureException * SQLErrorCodesSQLExceptionTranslator falls back to SQL state translation for IBM DB2 and MS SQL by default * added further default "sql-error-codes.xml" mappings JtaTransactionManager consistently throws TransactionSystemException in case of unexpected internal transaction state * JtaTransactionManager detects JBoss 4.2 transaction rollbacks caused by a timeout, throwing a meaningful

deadlock codes into ConcurrencyFailureException * SQLErrorCodesSQLExceptionTranslator falls back to SQL state translation for IBM DB2 and MS SQL by default * added further default "sql-error-codes.xml" mappings JtaTransactionManager consistently throws TransactionSystemException in case of unexpected internal transaction state * JtaTransactionManager detects JBoss 4.2 transaction rollbacks caused by a timeout, throwing a meaningful SingleConnectionFactory sets client ID before ExceptionListener (for providers with strict Connection state handling) * added "receiveTimeout" property to JmsInvokerClientInterceptor/ProxyFactoryBean (with

SingleConnectionFactory sets client ID before ExceptionListener (for providers with strict Connection state handling) * MessageListenerAdapter logs at warn level if a listener method returned a result but DispatcherServlet/Portlet * reworked DispatcherServlet/Portlet to automatically refresh internal state if its ApplicationContext refreshes * DispatcherPortlet logs startup logging at debug level instead null) * ConfigurableWebApplicationContext and ConfigurablePortletApplicationContext expose config state through getters * RequestContextListener works correctly even in case of the "requestDestroyed" callback

JtaTransactionManager consistently throws TransactionSystemException in case of unexpected internal transaction state * JtaTransactionManager detects JBoss 4.2 transaction rollbacks caused by a timeout, throwing a meaningful SingleConnectionFactory sets client ID before ExceptionListener (for providers with strict Connection state handling) * added "receiveTimeout" property to JmsInvokerClientInterceptor/ProxyFactoryBean (with DispatcherServlet/Portlet * reworked DispatcherServlet/Portlet to automatically refresh internal state if its ApplicationContext refreshes * DispatcherPortlet logs startup logging at debug level instead

DispatcherServlet/Portlet * reworked DispatcherServlet/Portlet to automatically refresh internal state if its ApplicationContext refreshes * DispatcherPortlet logs startup logging at debug level instead null) * ConfigurableWebApplicationContext and ConfigurablePortletApplicationContext expose config state through getters * RequestContextListener works correctly even in case of the "requestDestroyed" callback (not just action requests) * DispatcherPortlet restores LocaleContextHolder/RequestContextHolder state (e.g. from surrounding DispatcherServlet) Changes in version 2.0 final (3.10.2006) ------------