- 26 11月, 2015 1 次提交
-
-
由 Rossen Stoyanchev 提交于
-
- 25 11月, 2015 4 次提交
-
-
由 Sebastien Deleuze 提交于
-
由 Sebastien Deleuze 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Sebastien Deleuze 提交于
This is needed in order to be able to use Spring Reactive in standalone applications. These are temporary classes that will return in src/test/java when Spring Boot support for Reactive applications will be implemented.
-
- 23 11月, 2015 2 次提交
-
-
由 Rossen Stoyanchev 提交于
reactive.codec -> core.codec reactive.io -> util These may very well not be the final locations. For now they simply express that there are classes that belong somewhere in core, i.e. they are lower level dependencies than web.
-
由 Rossen Stoyanchev 提交于
This change adds an Encoder-to-MediaType lookup in ResponseBodyResultHandler to avoid MimeType to MediaType creation at runtime.
-
- 21 11月, 2015 2 次提交
-
-
由 Rossen Stoyanchev 提交于
RequestMappingHandlerMapping currently picks the first match and does have logic to deal with selecting the best match. This caused a random test failure depending on which controller method was matched first. This change removes the test.
-
由 Rossen Stoyanchev 提交于
-
- 14 11月, 2015 6 次提交
-
-
由 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).
-
由 Rossen Stoyanchev 提交于
-
由 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.
-
由 Rossen Stoyanchev 提交于
"Content-Type" is just a single MediaType. For the response, the MediaType must be fully selected before selecting and encoder. The ResponseBodyResultHandler now includes actual content negotiation with a potential 406 response.
-
由 Rossen Stoyanchev 提交于
-
由 Sebastien Deleuze 提交于
This commit introduces the following changes: - MessageToByteEncoder/Decoder renamed to Encoder/Decoder - JsonObjectEncoder/Decoder are now used directly in JacksonJsonEncoder/Decoder - Codec uses MimeType instead of MediaType since they are not specific to HTTP - Default MimeType are now managed thanks to Encoder/Decoder#getSupportedMimeTypes() - AbstractEncoder/Decoder takes care of generic MimeType related behavior
-
- 13 11月, 2015 1 次提交
-
-
由 Rossen Stoyanchev 提交于
-
- 07 11月, 2015 3 次提交
-
-
由 Marek Hawrylczak 提交于
-
由 Marek Hawrylczak 提交于
-
由 Marek Hawrylczak 提交于
-
- 31 10月, 2015 4 次提交
-
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
- 30 10月, 2015 7 次提交
-
-
由 Sebastien Deleuze 提交于
-
由 Sebastien Deleuze 提交于
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
Introduce HttpMessage hierarchy
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
-
- 29 10月, 2015 7 次提交
-
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
This commit introduces "reactive" sub-interfaces of the HttpMessage interface found in the Spring Framework.
-
由 Stephane Maldini 提交于
-
由 Stephane Maldini 提交于
Latest reactor-net doesn't depend on reactor-stream anymore (neither reactor-codec and reactor-bus, it only depends on reactor-core).
-
由 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
-
- 19 10月, 2015 2 次提交
-
-
由 Sebastien Deleuze 提交于
No need for rxjava-reactive-streams dependency and CompletableFutureUtils anymore.
-
由 Sebastien Deleuze 提交于
-
- 16 10月, 2015 1 次提交
-
-
由 Sebastien Deleuze 提交于
-