"equals" and "hashCode" such that all fields are respected * ClassPathBeanDefinitionScanner performs trace/debug logging during class resource introspection * ClassPathBeanDefinitionScanner ignores same class (not just after TransactionException) * TransactionSynchronizationManager interaction gets logged at trace level only (minimizing debug log per transaction) * JotmFactoryBean sets "defaultTimeout" value as "autocomplete") * JSF DelegatingVariableResolver and SpringBeanFacesELResolver log resolution success at trace level only Changes in version 2.5.4 (2008-04-28) ------------------------------------- General *

"equals" and "hashCode" such that all fields are respected * ClassPathBeanDefinitionScanner performs trace/debug logging during class resource introspection * ClassPathBeanDefinitionScanner ignores same class (not just after TransactionException) * TransactionSynchronizationManager interaction gets logged at trace level only (minimizing debug log per transaction) * JotmFactoryBean sets "defaultTimeout" value as "autocomplete") * JSF DelegatingVariableResolver and SpringBeanFacesELResolver log resolution success at trace level only Changes in version 2.5.4 (2008-04-28) ------------------------------------- General *

"autocomplete") * JSF DelegatingVariableResolver and SpringBeanFacesELResolver log resolution success at trace level only Changes in version 2.5.4 (2008-04-28) ------------------------------------- General * SmartInstantiationAwareBeanPostProcessor interface * AbstractBeanFactory does not log full exception stack trace (at debug level) on FactoryBean type check anymore * AbstractAutowireCapableBeanFactory allows for "logTargetClassInvocation" property to AbstractMonitoringInterceptor, for logging the target invocation trace Package org.springframework.beans * ConfigurablePropertyAccessor extends the TypeConverter interface

SmartInstantiationAwareBeanPostProcessor interface * AbstractBeanFactory does not log full exception stack trace (at debug level) on FactoryBean type check anymore * AbstractAutowireCapableBeanFactory allows for "logTargetClassInvocation" property to AbstractMonitoringInterceptor, for logging the target invocation trace Package org.springframework.beans * ConfigurablePropertyAccessor extends the TypeConverter interface springframework.remoting * RemoteInvocationUtils detects cycles in exception causes when updating the stack trace (avoiding an infinite loop) Package org.springframework.samples * added default Hibernate EntityManager

SmartInstantiationAwareBeanPostProcessor interface * AbstractBeanFactory does not log full exception stack trace (at debug level) on FactoryBean type check anymore * AbstractAutowireCapableBeanFactory allows for "logTargetClassInvocation" property to AbstractMonitoringInterceptor, for logging the target invocation trace Package org.springframework.beans * ConfigurablePropertyAccessor extends the TypeConverter interface springframework.remoting * RemoteInvocationUtils detects cycles in exception causes when updating the stack trace (avoiding an infinite loop) Package org.springframework.samples * added default Hibernate EntityManager

"logTargetClassInvocation" property to AbstractMonitoringInterceptor, for logging the target invocation trace Package org.springframework.beans * ConfigurablePropertyAccessor extends the TypeConverter interface springframework.remoting * RemoteInvocationUtils detects cycles in exception causes when updating the stack trace (avoiding an infinite loop) Package org.springframework.samples * added default Hibernate EntityManager "META-INF/aop.xml", "META-INF/spring.tld" and "META-INF/spring-form.tld" anymore * leverage the "trace" log level in the Spring core, to make activating the "debug" log level more bearable Package org

"logTargetClassInvocation" property to AbstractMonitoringInterceptor, for logging the target invocation trace Package org.springframework.beans * ConfigurablePropertyAccessor extends the TypeConverter interface springframework.remoting * RemoteInvocationUtils detects cycles in exception causes when updating the stack trace (avoiding an infinite loop) Package org.springframework.samples * added default Hibernate EntityManager "META-INF/aop.xml", "META-INF/spring.tld" and "META-INF/spring-form.tld" anymore * leverage the "trace" log level in the Spring core, to make activating the "debug" log level more bearable Package org

springframework.remoting * RemoteInvocationUtils detects cycles in exception causes when updating the stack trace (avoiding an infinite loop) Package org.springframework.samples * added default Hibernate EntityManager "META-INF/aop.xml", "META-INF/spring.tld" and "META-INF/spring-form.tld" anymore * leverage the "trace" log level in the Spring core, to make activating the "debug" log level more bearable Package org springframework.remoting * HTTP invoker and RMI invoker fill the client-side portion of the stack trace into transferred exceptions now * RmiClientInterceptorUtils throws clearer exception message in case

springframework.remoting * RemoteInvocationUtils detects cycles in exception causes when updating the stack trace (avoiding an infinite loop) Package org.springframework.samples * added default Hibernate EntityManager "META-INF/aop.xml", "META-INF/spring.tld" and "META-INF/spring-form.tld" anymore * leverage the "trace" log level in the Spring core, to make activating the "debug" log level more bearable Package org springframework.remoting * HTTP invoker and RMI invoker fill the client-side portion of the stack trace into transferred exceptions now * RmiClientInterceptorUtils throws clearer exception message in case

springframework.remoting * RemoteInvocationUtils detects cycles in exception causes when updating the stack trace (avoiding an infinite loop) Package org.springframework.samples * added default Hibernate EntityManager "META-INF/aop.xml", "META-INF/spring.tld" and "META-INF/spring-form.tld" anymore * leverage the "trace" log level in the Spring core, to make activating the "debug" log level more bearable Package org springframework.remoting * HTTP invoker and RMI invoker fill the client-side portion of the stack trace into transferred exceptions now * RmiClientInterceptorUtils throws clearer exception message in case