SPRING FRAMEWORK CHANGELOG =========================== http://www.spring.io Changes in version 3.2.18 (2016-12-21) ------------------------------------- fixed Constructor sets the source incorrectly in documentation of cache abstraction (SPR-14399) improved documentation og SpEL and Date Literals (SPR-14987) Changes in version 3.2.17 (2016-05-06) ------------------------------------- fixed AbstractRequestLoggingFilter lter appends null query string (SPR-14244) fixed Deadlock possible with AspectJ aspects and multi-threading (SPR-14241) fixed NPE thrown when calling methods with an empty @Caching annotation (SPR-14162)

SPRING FRAMEWORK CHANGELOG =========================== http://www.spring.io Changes in version 3.2.17 (2016-05-06) ------------------------------------- fixed AbstractRequestLoggingFilter appends null null query string (SPR-14244) fixed Deadlock possible with AspectJ aspects and multi-threading (SPR-14241) fixed NPE thrown when calling methods with an empty @Caching annotation (SPR-14162) fixed @RequestHeader handleExceptionInternal (SPR-13869) improved documentation at section 17.4 Handler mappings (SPR-13832) Changes in version 3.2.16 (2015-12-17) ------------------------------------- fixed Jdbc4SqlXmlHandler should

application server for transaction management? The Spring Framework’s transaction management support changes traditional rules as to when an enterprise Java application requires an application server. In SmartDataSource interface that wraps a single Connection that is not closed after each use. This is not multi-threading capable. If any client code calls close on the assumption of a pooled connection (as when using JTA transaction implementation. Both transaction demarcation and data access code work without changes, because they use the generic transaction management APIs. For distributed transactions across

singleton="true"/> Note: when deploying a bean in the prototype mode, the lifecycle of the bean changes slightly. By definition, Spring cannot manage the complete lifecycle of a non-singleton/prototype Spring. Important note: when deploying a bean in the prototype mode, the lifecycle of the bean changes slightly. By definition, Spring cannot manage the complete lifecycle of a non-singleton/prototype (in the case of the BeanFactory) or automatically (in the case of the ApplicationContext) to apply changes of some sort to an entire BeanFactory, after it has been constructed. Spring includes a number of

singleton="true"/> Note: when deploying a bean in the prototype mode, the lifecycle of the bean changes slightly. By definition, Spring can not manage the complete lifecycle of a non-singleton/prototype Spring. Important note: when deploying a bean in the prototype mode, the lifecycle of the bean changes slightly. By definition, Spring can not manage the complete lifecycle of a non-singleton/prototype (in the case of the BeanFactory) or automatically (in the case of the ApplicationContext) to apply changes of some sort to an entire BeanFactory, after it has been constructed. Spring includes a number of

singleton="true"/> Note: when deploying a bean in the prototype mode, the lifecycle of the bean changes slightly. By definition, Spring cannot manage the complete lifecycle of a non-singleton/prototype Spring. Important note: when deploying a bean in the prototype mode, the lifecycle of the bean changes slightly. By definition, Spring cannot manage the complete lifecycle of a non-singleton/prototype (in the case of the BeanFactory) or automatically (in the case of the ApplicationContext) to apply changes of some sort to an entire BeanFactory, after it has been constructed. Spring includes a number of

singleton="true"/> Note: when deploying a bean in the prototype mode, the lifecycle of the bean changes slightly. By definition, Spring cannot manage the complete lifecycle of a non-singleton/prototype Spring. Important note: when deploying a bean in the prototype mode, the lifecycle of the bean changes slightly. By definition, Spring cannot manage the complete lifecycle of a non-singleton/prototype (in the case of the BeanFactory) or automatically (in the case of the ApplicationContext) to apply changes of some sort to an entire BeanFactory, after it has been constructed. Spring includes a number of

singleton="true"/> Note: when deploying a bean in the prototype mode, the lifecycle of the bean changes slightly. By definition, Spring cannot manage the complete lifecycle of a non-singleton/prototype Spring. Important note: when deploying a bean in the prototype mode, the lifecycle of the bean changes slightly. By definition, Spring cannot manage the complete lifecycle of a non-singleton/prototype (in the case of the BeanFactory) or automatically (in the case of the ApplicationContext) to apply changes of some sort to an entire BeanFactory, after it has been constructed. Spring includes a number of

singleton="true"/> Note: when deploying a bean in the prototype mode, the lifecycle of the bean changes slightly. By definition, Spring cannot manage the complete lifecycle of a non-singleton/prototype Spring. Important note: when deploying a bean in the prototype mode, the lifecycle of the bean changes slightly. By definition, Spring cannot manage the complete lifecycle of a non-singleton/prototype (in the case of the BeanFactory) or automatically (in the case of the ApplicationContext) to apply changes of some sort to an entire BeanFactory, after it has been constructed. Spring includes a number of

singleton="true"/> Note: when deploying a bean in the prototype mode, the lifecycle of the bean changes slightly. By definition, Spring cannot manage the complete lifecycle of a non-singleton/prototype Spring. Important note: when deploying a bean in the prototype mode, the lifecycle of the bean changes slightly. By definition, Spring cannot manage the complete lifecycle of a non-singleton/prototype (in the case of the BeanFactory) or automatically (in the case of the ApplicationContext) to apply changes of some sort to an entire BeanFactory, after it has been constructed. Spring includes a number of