- 22 8月, 2018 1 次提交
-
-
由 横云断岭 提交于
-
- 21 8月, 2018 1 次提交
-
-
由 Brian Clozel 提交于
When used as global Netty resources, ReactorResourceFactory creates and sets those resources on Reactor's HttpResources directly. When that ReactorResourceFactory bean is destroyed, those resources are disposed but HttpResources still holds a reference to those and may try to use them again. This commit uses HttpResources to clear those resources and its references to it, when the ReactorResourceFactory is treating those as global. Issue: SPR-17199
-
- 20 8月, 2018 2 次提交
-
-
由 Stephane Nicoll 提交于
* pr/1934: Fix usage of deprecated functionality in docs
-
由 Kyle Carter 提交于
Closes gh-1934
-
- 19 8月, 2018 1 次提交
-
-
由 Sam Brannen 提交于
Issue: SPR-17174
-
- 18 8月, 2018 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-17160
-
- 17 8月, 2018 8 次提交
-
-
由 Juergen Hoeller 提交于
Includes XMLUnit 2.6.1 and Undertow 2.0.13. Issue: SPR-16115
-
由 Juergen Hoeller 提交于
Issue: SPR-17191
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
This reverts commit 29ce6685.
-
由 Sebastien Deleuze 提交于
Issue: SPR-17179
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-17174
-
由 Sebastien Deleuze 提交于
JettyResourceFactory, similar to ReactorResourceFactory, allows to share resources (Executor, ByteBufferPool, Scheduler) between Jetty clients and servers. Issue: SPR-17179
-
- 16 8月, 2018 10 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-17189
-
由 Rossen Stoyanchev 提交于
-
由 Juergen Hoeller 提交于
Includes upgrade to Hibernate ORM 5.3.5, EclipseLink 2.7.3, Selenium HtmlUnit Driver 2.32.1, Jetty 9.4.12 RC2.
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-17188
-
由 Stephane Nicoll 提交于
-
由 Brian Clozel 提交于
-
由 Brian Clozel 提交于
Prior to this commit, when using the `SimpleClientHttpRequestFactory` as a driver for `RestTemplate`, the HTTP response body would only be drained if there was an attempt to read it in the first place. This commit ensures that, even if there's no attempt at reading the response body, it is properly drained when the response is closed to make sure that the connection is released in a proper state and can be put back in the connection pool for reuse. Issue: SPR-17181
-
由 Brian Clozel 提交于
When dealing with `Optional` values in a Controller handler (for example, values coming from a Spring Data repository), developers might reuse this code snippet quite often: ``` @GetMapping("/user") public ResponseEntity<Optional<User>> fetchUser() { Optional<User> user = //... return user.map(ResponseEntity::ok).orElse(notFound().build()); } ``` This commit adds a new static method on `ResponseEntity` for that, simplifying the previous snippet with `return ResponseEntity.of(user);` Note that in case more specific HTTP response headers are required by the application, developers should use other static methods to explicitly tell which headers should be used in each case. Issue: SPR-17187
-
- 15 8月, 2018 14 次提交
-
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
Issue: SPR-17129
-
由 Juergen Hoeller 提交于
Includes caching of declared annotation arrays and combined searching for several annotation types (used in SpringCacheAnnotationParser). Issue: SPR-16933
-
由 Sam Brannen 提交于
Issue: SPR-17006
-
由 Sam Brannen 提交于
Prior to this commit, if a test class was meta-annotated with multiple @BootstrapWith declarations that registered different TestContextBootstrapper implementations, such a configuration would result in an IllegalStateException, and there was no way to override this behavior. This commit addresses this shortcoming by relaxing the explicit TestContextBootstrapper resolution in BootstrapUtils so that a directly present @BootstrapWith annotation will now override declarations of @BootstrapWith that are meta-present. In other words, if @BootstrapWith is used as a meta-annotation, it can be overridden directly on the test class via an explicit, local declaration of @BootstrapWith. Issue: SPR-17006
-
由 Sam Brannen 提交于
-
由 Brian Clozel 提交于
This reverts commit 7e917335.
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
-
由 Brian Clozel 提交于
This commit handles "empty" cases for `ResponseEntity` controller handler return types when wrapped with a `java.util.Optional` in Spring MVC or a single `Publisher` like `Mono`. Given the following example for Spring MVC: ``` @GetMapping("/user") public Optional<ResponseEntity<User>> fetchUser() { Optional<User> user = //... return user.map(ResponseEntity::ok); } ``` If the resulting `Optional` is empty, Spring MVC will infer a `ResponseEntity` with an empty body and a 404 HTTP response status. The same reasoning is applied to Spring WebFlux with Publisher types: ``` @GetMapping("/user") public Mono<ResponseEntity<User>> fetchUser() { Mono<User> user = //... return user.map(ResponseEntity::ok); } ``` This feature is only valid for `HttpEntity` return types and does not apply to `@ResponseBody` controller handlers. Issue: SPR-13281
-
由 Rossen Stoyanchev 提交于
Issue: SPR-17178
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-17180 Issue: SPR-17182
-
由 Juergen Hoeller 提交于
Includes Groovy 2.5.2, Undertow 2.0.12, Hibernate Validator 6.0.12. Issue: SPR-17129
-
- 14 8月, 2018 2 次提交
-
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
Rename "Builder" sub-section to "Configuration" and move it in the beginning before all others since it explains how to create a client in the first place. Update content on Reactor Netty connector based on the API in 0.8 and specifically address Reactor Netty resources and lifecycle. Issue: SPR-16963
-