- 22 11月, 2019 6 次提交
-
-
由 Rossen Stoyanchev 提交于
Closes gh-24050
-
由 Sébastien Deleuze 提交于
Closes gh-24059
-
由 Sébastien Deleuze 提交于
Closes gh-23758
-
由 Sébastien Deleuze 提交于
This commit refines Coroutines annotated controller support by considering Kotlin Unit as Java void and using the right ReactiveAdapter to support all use cases, including suspending functions that return Flow (usual when using APIs like WebClient). It also fixes RSocket fire and forget handling and adds related tests for that use case. Closes gh-24057 Closes gh-23866
-
由 Rossen Stoyanchev 提交于
Before this commit the connector waited for a completed response (via ServerHttpResponse#setComplete or ServerHttpResponse#writeWith) or an error signal in handling, but it didn't deal explicitly with the case where both can occur. This commit explicitly waits for the completion of handling (success or error) before passing the response downstream. If an error occurs after response completion, it is wrapped in a dedicated exception that also provides access to the completed response. Close gh-24051
-
由 Juergen Hoeller 提交于
Closes gh-24048
-
- 21 11月, 2019 6 次提交
-
-
由 stsypanov 提交于
-
由 Qimiao Chen 提交于
Closes gh-24048
-
由 Juergen Hoeller 提交于
-
由 Rossen Stoyanchev 提交于
This commit allows single-value async producers for the values of metadata entries in both the SETUP and for requests. The same is also enabled for data in the SETUP frame. Close gh-23640
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Closes gh-24042
-
- 20 11月, 2019 5 次提交
-
-
由 Arjen Poutsma 提交于
Closes gh-23342
-
由 Stephane Nicoll 提交于
See gh-24037
-
由 Rossen Stoyanchev 提交于
Close gh-24030
-
由 Sam Brannen 提交于
The test introduced in this commit is intended to serve as a regression test for the status quo. See gh-23985
-
由 Rossen Stoyanchev 提交于
See gh-23999
-
- 19 11月, 2019 10 次提交
-
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
-
由 Juergen Hoeller 提交于
Closes gh-24029
-
由 Juergen Hoeller 提交于
Closes gh-24023
-
由 Sam Brannen 提交于
Prior to this commit, methods in a @ControllerAdvice bean were registered and invoked twice if the advice was a scoped bean (e.g., request or session scoped). In other words, both the proxy bean and the target bean were wrapped in ControllerAdviceBean instances. This commit fixes this bug by modifying the findAnnotatedBeans() method in ControllerAdviceBean so that it filters out targets of scoped proxies. Closes gh-24017
-
由 Sébastien Deleuze 提交于
Closes gh-24006
-
由 Arjen Poutsma 提交于
See gh-23365
-
由 Sam Brannen 提交于
Spring Framework 5.2 introduced support for implementing the Ordered interface in a @ControllerAdvice bean. This support requires that @ControllerAdvice beans be eagerly resolved from the BeanFactory in order to invoke the getOrder() method defined in the Ordered interface. Unfortunately doing so resulted in a regression in that an attempt to eagerly resolve a scoped @ControllerAdvice bean throws a BeanCreationException due to the lack of an active scope (e.g., request or session scope). This commit fixes this regression by avoiding eager resolution of scoped @ControllerAdvice beans. As a direct consequence, the Ordered interface is not supported for scoped @ControllerAdvice beans. Closes gh-23985
-
由 Sam Brannen 提交于
-
由 Rossen Stoyanchev 提交于
Before this change an @MessageMapping could be matched to any RSocket interaction type, which is arguably too flexible, makes it difficult to reason what would happen in case of a significant mismatch of cardinality, e.g. request for Fire-And-Forget (1-to-0) mapped to a method that returns Flux, and could result in payloads being ignored, or not seen unintentionally. This commit checks @ConnectMapping method on startup and rejects them if they return any values (sync or async). It also refines each @MessageMapping to match only the RSocket interaction type it fits based on the input and output cardinality of the handler method. Subsequently if a request is not matched, we'll do a second search to identify partial matches (by route only) and raise a helpful error that explains which interaction type is actually supported. The reference docs has been updated to explain the options. Closes gh-23999
-
- 18 11月, 2019 1 次提交
-
-
由 Sam Brannen 提交于
-
- 17 11月, 2019 1 次提交
-
-
由 denisgalaybo 提交于
Closes gh-24008
-
- 15 11月, 2019 8 次提交
-
-
由 Sam Brannen 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Rossen Stoyanchev 提交于
Closes gh-1885
-
由 Rossen Stoyanchev 提交于
See gh-1885
-
由 Mark Hobson 提交于
Issue: SPR-17040
-
由 Rossen Stoyanchev 提交于
Closes gh-23994
-
由 Juergen Hoeller 提交于
Closes gh-23996
-
- 14 11月, 2019 3 次提交
-
-
由 Sam Brannen 提交于
-
由 Sébastien Deleuze 提交于
This commit adds support for Continuation parameter that is now considered as an optional parameter since it is never provided by the user. It also simplifies and optimizes the implementation. Closes gh-23991
-
由 Sam Brannen 提交于
-