- 20 3月, 2013 1 次提交
-
-
由 Juergen Hoeller 提交于
General JPA 2.0+ requirement; upgraded build and tests to EclipseLink 2.4, OpenJPA 2.2, Hibernate 3.6
-
- 19 3月, 2013 17 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
- 14 3月, 2013 5 次提交
-
-
由 Phillip Webb 提交于
* 3.2.x: (28 commits) Hide 'doc' changes from jdiff reports Document @Bean 'lite' mode vs @Configuration Final preparations for 3.2.2 Remove Tiles 3 configuration method Polishing Extracted buildRequestAttributes template method from FrameworkServlet Added "beforeExistingAdvisors" flag to AbstractAdvisingBeanPostProcessor Minor refinements along the way of researching static CGLIB callbacks Compare Kind references before checking log levels Polish Javadoc in RequestAttributes Fix copy-n-paste errors in NativeWebRequest Fix issue with restoring included attributes Add additional test for daylight savings glitch Document context hierarchy support in the TCF Fix test for daylight savings glitch Make the methodParameter field of HandlerMethod final Disable AsyncTests in spring-test-mvc Reformat the testing chapter Document context hierarchy support in the TCF Document context hierarchy support in the TCF ...
-
由 Phillip Webb 提交于
-
由 Phillip Webb 提交于
Rework the reference documentation to better distinguish the differences between @Bean methods used in @Comonent vs @Configuration classes. The 'Using the @Bean annotation' section now only covers concepts applicable when using @Bean methods in @Configuration _or_ @Component classes. Information only applicable to @Configuration classes has been moved to a new 'Using the @Configuration annotation' section. An additional sidebar section attempts to explain the differences between the two approaches. Issue: SPR-9425
-
由 Juergen Hoeller 提交于
-
由 Rossen Stoyanchev 提交于
Issue: SPR-10361
-
- 13 3月, 2013 8 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Also, RequestBindingInterceptor now obtains HttpServletRequest from locally passed-in request handle and delegates to buildRequestAttributes as well now. Issue: SPR-10342
-
由 Juergen Hoeller 提交于
Just AsyncAnnotationBeanPostProcessor switches "beforeExistingAdvisors" to "true" by default. So effectively, MethodValidation/PersistenceExceptionTranslationPostProcessor apply after existing advisors by default again, fixing the 3.1->3.2 regression. Issue: SPR-10309
-
由 Juergen Hoeller 提交于
Specifically, our CallbackFilter doesn't hold an implicit reference to the containing ConfigurationClassEnhancer class anymore. Issue: SPR-10307
-
由 Phillip Webb 提交于
# By David Harkness * patch-1: Compare Kind references before checking log levels
-
由 David Harkness 提交于
Assuming reference comparisons are much quicker than checking likely-nested logger levels, perform the former first. Also, since the reference can match only one of the instances, use "else if" to short-circuit the search.
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
-
- 11 3月, 2013 7 次提交
-
-
由 Rossen Stoyanchev 提交于
Before this change the DispatcherServlet restored modified and also removed added attributes but did not restore removed attributes. Issue: SPR-10360
-
由 Sam Brannen 提交于
# By Dave Syer * dsyer-feature/crontest: Add additional test for daylight savings glitch
-
由 Dave Syer 提交于
The problem was that clocks go forward *at* 2am, so 2am doesn't exist once a year. Users might be surprised that their cron trigger doesn't go off one night, but that is arguably correct (and what happens now). The test can be modified if we decide to change the trigger behaviour.
-
由 Sam Brannen 提交于
This commit updates the reference manual regarding the new support for @ContextHierarchy and hierarchy modes in @DirtiesContext. Issue: SPR-10357
-
由 Chris Beams 提交于
Fix test for daylight savings glitch
-
由 Dave Syer 提交于
-
由 Rossen Stoyanchev 提交于
Previously the methodParameter array field was initialized lazily since it requires reflection. However, in practice the field is always used and there is not much benefit from the lazy initialization. In Spring Framework 3.2, the methodParameter field was copied when a new HandlerMethod instance (with the resolved bean) is created for performance reasons. That introduced a synchronization issue since the lazy initialization was not synchronized. Issue: SPR-10365
-
- 10 3月, 2013 2 次提交
-
-
由 Rossen Stoyanchev 提交于
-
由 Sam Brannen 提交于
This commit reformats the testing chapter (and adds minor polishing changes) in order to avoid massive merge diffs in upcoming commits. Issue: SPR-10357
-