- 27 11月, 2018 1 次提交
-
-
由 Spring Buildmaster 提交于
-
- 26 11月, 2018 2 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-17536
-
由 Juergen Hoeller 提交于
ResolvableType-based matching consistently respects generic factory method return type (even for pre-initialized raw singleton instance) Issue: SPR-17524 (cherry picked from commit ebbe14c3)
-
- 24 11月, 2018 6 次提交
-
-
由 Juergen Hoeller 提交于
Also includes Hibernate ORM 5.1.16 for integration tests.
-
由 Juergen Hoeller 提交于
Also includes Apache HttpClient 4.5.6 and HttpAsyncClient 4.1.4.
-
由 Juergen Hoeller 提交于
Issue: SPR-17439
-
由 Juergen Hoeller 提交于
(cherry picked from commit 77ab88b1)
-
由 Sam Brannen 提交于
Prior to this commit, parallel invocations of MethodParameter.findParameterIndex() (invoked indirectly via SynthesizingMethodParameter.forParameter() and MethodParameter.forParameter()) could intermittently lead to an IllegalArgumentException being thrown due to a race condition in the internal implementation of the JDK's java.lang.reflect.Executable.getParameters() method. This commit addresses this issue by introducing a fallback for-loop that iterates over the candidate parameters a second time using equality checks instead of identity checks. Issue: SPR-17534 (cherry-picked from commit 81fde5ec)
-
由 Sam Brannen 提交于
Prior to this commit, parallel execution of @BeforeEach and @AfterEach methods that accepted @Autowired arguments would fail intermittently due to a race condition in the internal implementation of the JDK's java.lang.reflect.Executable.getParameters() method. This commit addresses this issue by creating instances of SynthesizingMethodParameter via SynthesizingMethodParameter.forExecutable(Executable, int) instead of SynthesizingMethodParameter.forParameter(Parameter), since the latter looks up the parameter index by iterating over the array returned by Executable.getParameters() (which is not thread-safe). Issue: SPR-17533
-
- 23 11月, 2018 8 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-17486
-
由 Juergen Hoeller 提交于
Issue: SPR-17492
-
由 Juergen Hoeller 提交于
Issue: SPR-15540 (cherry picked from commit bf272b0b)
-
由 Juergen Hoeller 提交于
LocalResourceCache properly initializes cacheLimit on construction. Issue: SPR-17527 (cherry picked from commit 262c702d)
-
由 Juergen Hoeller 提交于
Issue: SPR-17508 (cherry picked from commit f5aeb814)
-
- 22 11月, 2018 1 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-17525
-
- 21 11月, 2018 3 次提交
-
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
Issue: SPR-17518
-
由 Brian Clozel 提交于
See SPR-17502
-
- 19 11月, 2018 1 次提交
-
-
由 Brian Clozel 提交于
Prior to this commit, when errors happened before the response was committed, the `Content-Length` response header would be left as is. This can be problematic since the error can be handled later in the chain and the response body changed accordingly. For example, Spring Boot renders error pages in those cases. If the `Content-Length` is set, HTTP clients can get confused and only consider part of the error response body. This commit ensures that any `Content-Length` response header is removed in case of errors, if the response is not already committed. This is done at the `AbstractServerHttpResponse` level, since errors can be handled in multiple places and the response itself is the safest place to handle this case. As a consequence, this commit also removes `Content-Length` checks in `EncoderHttpMessageWriter` since we now consider that we should rely on the response body we're about to write rather than any previously set value. Issue: SPR-17502 (Cherry-picked from 3203d398)
-
- 17 11月, 2018 1 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-17501
-
- 10 11月, 2018 1 次提交
-
-
由 Rossen Stoyanchev 提交于
Unlike 5,1, TEMPLATE_AND_VALUES is not the default encoding mode. Nevertheless when that mode is used, it should work consistently. Issue: SPR-17465
-
- 09 11月, 2018 2 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-17473
-
由 Juergen Hoeller 提交于
Issue: SPR-14514 Issue: SPR-15600
-
- 08 11月, 2018 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-17476 (cherry picked from commit 362c59c3)
-
- 06 11月, 2018 8 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-17306
-
由 Juergen Hoeller 提交于
(cherry picked from commit 5e7a8b27)
-
由 Juergen Hoeller 提交于
Issue: SPR-17445 (cherry picked from commit ea3250c8)
-
由 Juergen Hoeller 提交于
Issue: SPR-17442 (cherry picked from commit b1f5f515)
-
由 Juergen Hoeller 提交于
Issue: SPR-17448 (cherry picked from commit 59fa647e)
-
由 Juergen Hoeller 提交于
Includes deprecation of NON_BRIDGED_METHODS constant. Issue: SPR-17464 (cherry picked from commit 0a7dcf14)
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
Issue: SPR-17469
-
- 02 11月, 2018 1 次提交
-
-
由 Rossen Stoyanchev 提交于
After the fix #658c7f for lenient parsing of dates, the error message raised uses an HttpHeaders-formatted date. As a result the test verifying the error message fails in the beginning of the month between 1-9 because it's formatted slightly differently.
-
- 27 10月, 2018 2 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-16636
-
由 Juergen Hoeller 提交于
Issue: SPR-17374 (cherry picked from commit dc1e3b46)
-
- 26 10月, 2018 2 次提交
-
-
由 Brian Clozel 提交于
Prior to this commit, no `ResourceUrlProvider` was configured in WebFlux (no bean was contributed by the WebFlux infrastructure). Also, several `ResourceTransformer` instances that extend the `ResourceTransformerSupport` base class need a `ResourceUrlProvider` to resolve absolute URLs when rewriting resource URLs. At this point, no `ResourceUrlProvider` was configured and they could only resolve relative URLs. This commit contributes a new `ResourceUrlProvider` to the WebFlux configuration; this bean can be reused by the WebFlux infrastructure and application code. This also automatically configure this shared `ResourceUrlProvider` instance on the resource chain where needed. Issue: SPR-17433 (Cherry-picked from fc957e95)
-
由 Juergen Hoeller 提交于
-