- 12 6月, 2015 1 次提交
-
-
由 Sam Brannen 提交于
The modifications to DefaultMockMvcBuilder performed in conjunction with SPR-12553 introduced a breaking change: the WebApplicationContext supplied to DefaultMockMvcBuilder's constructor was *always* stored in the ServletContext as the root WebApplicationContext, overwriting a root WebApplicationContext that had been set by the user or by the Spring TestContext Framework (TCF) -- for example, in AbstractGenericWebContextLoader. Consequently, the changes in SPR-12553 cause tests that use @ContextHierarchy to fail if web components rely on the correct WebApplicationContext being stored under the WebApplicationContext#ROOT_WEB_APPLICATION_CONTEXT_ATTRIBUTE key. This commit reverts the breaking changes introduced in SPR-12553: if the root WebApplicationContext has already been set in the ServletContext of the WebApplicationContext supplied to DefaultMockMvcBuilder, no action is taken. Furthermore, this commit introduces new code to address the initial intent of SPR-12553. Specifically, if the root WebApplicationContext has NOT been set in the ServletContext of the WebApplicationContext supplied to DefaultMockMvcBuilder, the application context hierarchy will be traversed in search of the root WebApplicationContext, and the root WebApplicationContext will then be stored under the ROOT_WEB_APPLICATION_CONTEXT_ATTRIBUTE key. Issue: SPR-13075, SPR-12553
-
- 11 6月, 2015 8 次提交
-
-
由 Brian Clozel 提交于
-
由 Brian Clozel 提交于
Prior to this change, the `"Last-Modified"` and "`Etag`" support had been improved with SPR-11324: HTTP response headers are now automatically added for conditional requests and more. This commit fixes the format of the "`Last-Modified`" and "`ETag`" values, which were using an epoch timestamp rather than an HTTP-date format defined in RFC 7231 section 7.1.1.1. Also, Conditional responses are only applied when the given response applies, i.e. when it has an compatible HTTP status (2xx). Issue: SPR-13090
-
由 Juergen Hoeller 提交于
Issue: SPR-13102
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-13112
-
由 Juergen Hoeller 提交于
Issue: SPR-13108
-
由 Juergen Hoeller 提交于
Issue: SPR-13101
-
由 Rossen Stoyanchev 提交于
Issue: SPR-13104
-
- 10 6月, 2015 3 次提交
-
-
由 Arjen Poutsma 提交于
This commit introduces support for RFC 7239: Forwarded HTTP Extension in the UriComponentsBuilder. Unfortunately, RFC 7239 is not a complete replacement for the X-Forwarded-* headers: specifically, there is not direct replacement for X-Forwarded-Port. The JIRA contains more information. Issue: SPR-11856
-
由 Juergen Hoeller 提交于
Issue: SPR-11807
-
由 Juergen Hoeller 提交于
-
- 09 6月, 2015 3 次提交
-
-
由 Stephane Nicoll 提交于
Provide a mean to detect the actual ResolvableType based on a instance as a counter measure to type erasure. Upgrade the event infrastructure to detect if the event (or the payload) implements such interface. When this is the case, the return value of `getResolvableType` is used to validate its generic type against the method signature of the listener. Issue: SPR-13069
-
由 Juergen Hoeller 提交于
Issue: SPR-13103
-
由 Juergen Hoeller 提交于
-
- 05 6月, 2015 12 次提交
-
-
由 Sebastien Deleuze 提交于
This commit introduces the following changes: - configureCors(CorsConfigurer configurer) is renamed to addCorsMappings(CorsRegistry registry) - enableCors(String... pathPatterns) is renamed to addMapping(String pathPattern) - <cors /> element must have at least one <mapping /> child element in order to be consistent with XML based configuration and have more explicit configuration Issues: SPR-12933, SPR-13046
-
由 Stephane Nicoll 提交于
While working on SPR-12532, an extra IdentityWrapper was added to work around a backward compatible issue between commons pool 1.x and 2.x. This issue (POOL-283) has actually been fixed in 2.4 and their IdentityWrapper is using object equality so our wrapper is in the way. Looking retrospectively, the code looks all fine without the workaround and commons pool 2.4 or later so it has been removed.
-
由 Sebastien Deleuze 提交于
Issue: SPR-13097
-
由 Brian Clozel 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Also removes "throws Exception" declaration from ThreadPoolExecutorFactoryBean's getObject method. Issue: SPR-13095
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-13076
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
Issue: SPR-11393
-
由 Sam Brannen 提交于
Issue: SPR-11393
-
由 Sam Brannen 提交于
-
- 04 6月, 2015 3 次提交
-
-
由 Sam Brannen 提交于
Issue: SPR-13091
-
由 Sam Brannen 提交于
Issue: SPR-11393
-
由 Sam Brannen 提交于
Issue: SPR-11393
-
- 03 6月, 2015 3 次提交
-
-
由 Stephane Nicoll 提交于
Since Spring 4.1, a CacheResolver may be configured to customize the way the cache(s) to use for a given cache operation are retrieved. Since a CacheResolver implementation may not use the cache names information at all, this attribute has been made optional. However, a fix was still applied, preventing a Cache operation without a cache name to be defined properly. We now allow this valid use case. Issue: SPR-13081
-
由 Stephane Nicoll 提交于
Issue: SPR-13071
-
由 Sebastien Deleuze 提交于
This commit introduces support for this kind of CORS XML namespace configuration: <mvc:cors> <mvc:mapping path="/api/**" allowed-origins="http://domain1.com, http://domain2.com" allowed-methods="GET, PUT" allowed-headers="header1, header2, header3" exposed-headers="header1, header2" allow-credentials="false" max-age="123" /> <mvc:mapping path="/resources/**" allowed-origins="http://domain1.com" /> </mvc:cors> Issue: SPR-13046
-
- 02 6月, 2015 3 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-13091
-
由 Juergen Hoeller 提交于
Issue: SPR-13089
-
由 Juergen Hoeller 提交于
Includes other recent dependency updates (JRuby 1.7.20, Jetty 9.2.11, Tomcat 8.0.23, Reactor 2.0.3) Issue: SPR-13088
-
- 01 6月, 2015 4 次提交
-
-
由 Esko Luontola 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Jasper de Vries 提交于
-
由 Rossen Stoyanchev 提交于
-