- 23 7月, 2016 1 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-14159
-
- 08 7月, 2016 1 次提交
-
-
由 Rossen Stoyanchev 提交于
-
- 04 7月, 2016 2 次提交
-
-
由 Rossen Stoyanchev 提交于
When using the ConversionService to check and bridge to and from reactive types we now generallly provide the full type information available from method signatures. However that full type information is not always necessary such as when we perform additional checks on the generics of the reactive type (e.g. Mono<ResponseEntity>). This allows us to switch to use DefaultFormattingConversionService instead of GenericConversionService while also ensuring that the CollectionToObjectConverter doesn't think it can convert List<?> to any reactive type. The ObjectToObjectConverter can also interfere because it is smart enough to find the "from(Publisher<?>)" method on Flux and Mono. To make up for that on the response side we now check if a type is assignable to Publisher first in which case it is a simple cast. In turn that means we don't need a PublisherToFluxConverter which can be problematic in its own right because it can convert from Mono to Flux which technically doesn't lose data but switches stream semantics. Issue: #124, #128
-
由 Rossen Stoyanchev 提交于
HandlerAdapter's should always be able to provide a MethodParameter which in turn ensures that HandlerResultHandler's have full type information from method declarations. This commit also introduces ResolvableMethod for use in tests to make it easy to obtain MethodParameter return types. Issue: #128
-
- 02 7月, 2016 1 次提交
-
-
由 Sebastien Deleuze 提交于
This commit replaces Reactive Streams converters for RxJava1 and CompletableFuture with Reactor specific ones. The results in conversion that preserves stream semantics, i.e. Mono vs Flux. For example this is allowed: Flux -> Observable Mono -> Single Mono -> CompletableFuture This is not allowed: Flux -> Single Mono -> Observable Flux -> CompletableFuture As a result it is now possible to check through the ConversionService if a target type to convert to is a stream of many or of one which is useful for decoding purposes. The commit also adds PublisherToFluxConverter to allow conversion from raw Publisher to Flux. The reverse is not necessary since Flux is a Publisher and it's a no-op conversion.
-
- 01 6月, 2016 1 次提交
-
-
由 Rossen Stoyanchev 提交于
-
- 15 4月, 2016 2 次提交
-
-
由 Rossen Stoyanchev 提交于
The new package is parallel to the "mvc" package under spring-webmvc and a place to hold the various programming model styles.
-
由 Rossen Stoyanchev 提交于
- correct name of HttpHandlerHandlerAdapter to WebHandlerHandlerAdapter - shorten SimpleHandlerResultHandler to SimpleResultHandler - add HandlerResult constructor without Model - update tests
-
- 04 3月, 2016 2 次提交
-
-
由 Stephane Maldini 提交于
-
由 Stephane Maldini 提交于
-
- 27 2月, 2016 1 次提交
-
-
由 Stephane Maldini 提交于
-
- 09 2月, 2016 1 次提交
-
-
由 Rossen Stoyanchev 提交于
A model is created and passed to argument resolvers including a new ModelArgumentResolver. The model is then exposed for result handling as a field in HandlerResult.
-
- 07 1月, 2016 1 次提交
-
-
由 Sebastien Deleuze 提交于
Flux and Mono are used both for implementation and exposed at API level to express 1 versus N semantic and to provide default Rx operators: - Flux<T> for multiple values Publisher (issue #48) - Mono<T> for single value Publisher (issue #50) - Mono<Void> for Publisher with no value (issue #49)
-
- 30 11月, 2015 1 次提交
-
-
由 Sebastien Deleuze 提交于
-
- 25 11月, 2015 1 次提交
-
-
由 Sebastien Deleuze 提交于
-
- 14 11月, 2015 2 次提交
-
-
由 Rossen Stoyanchev 提交于
The web related code is now under org.springframework.web.reactive. This is parallel to org.springframework.web (the top-level package of spring-webmvc).
-
由 Sebastien Deleuze 提交于
This change allows to be able to check generic type on the return value at HandlerAdapter and ResultHandler level. For example, it allows to do a Publisher<Void> check in SimpleHandlerResultHandler.
-
- 31 10月, 2015 2 次提交
-
-
由 Rossen Stoyanchev 提交于
-
- 29 10月, 2015 1 次提交
-
-
由 Sebastien Deleuze 提交于
This commit introduces the following changes: - Publisher -> Observable/Stream/etc. conversion is now managed in a dedicated ConversionService instead of directly in RequestBodyArgumentResolver and ResponseBodyResultHandler - More isolated logic that decides if the stream should be serialized as a JSON array or not - Publisher<ByteBuffer> are now handled by regular ByteBufferEncoder and ByteBufferDecoder - Handle Publisher<Void> return value properly - Ensure that the headers are properly written even for response without body - Improve JsonObjectEncoder to autodetect JSON arrays
-
- 03 10月, 2015 1 次提交
-
-
由 Sebastien Deleuze 提交于
This commit updates HandlerAdapter#handle() to return HandlerResult instead of Publisher<HandlerResult>. A new SimpleHandlerResultHandler class has been introduced for handlers returning Publisher<Void>.
-