- 17 9月, 2016 13 次提交
-
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
Refactor BodyInsertor to expose insertion logic directly, rather than exposing a writer function and supplier.
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
Fixed package tangle between w.r.f.RequestPredicates and w.r.f.support.RequestWrapper.
-
由 Rossen Stoyanchev 提交于
Move the AbstractServletHttpHandlerAdapterInitializer together with the other two base classes in spring-web-reactive. Since the interface is in the web package, this avoids a package cycle. Also add a mention in the reference. Issue: SPR-14713
-
由 Arjen Poutsma 提交于
This commit introduces three new WebApplicationInitializers for use with Spring Web Reactive: - The AbstractServletHttpHandlerAdapterInitializer registers a ServletHttpHandlerAdapter that wraps a user-provided HttpHandler. - The AbstractDispatcherHandlerInitializer registers a ServletHttpHandlerAdapter that wraps a DispatcherHandler (or any WebHandler). The handler is provided with an application context. - The AbstractAnnotationConfigDispatcherHandlerInitializer is a subclass of the above, creating an AnnotationConfigApplicationContext based no provided @Configuration classes. Issue: SPR-14713
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
This commit refactors the response body extraction logic into a separate function: BodyExtractor. Standard populators can be found in BodyExtractors.
-
由 Arjen Poutsma 提交于
This commit extracts the response body insertion logic into a separate strategy interface: BodyPopulator. Standard populators can be found in BodyPopulators.
-
由 Arjen Poutsma 提交于
This commit refactors the Router into a RoutingFunctions class, by: - Renaming the class :) - Moving all Configuration logic into a separate, top-level Configuration class with mutable builder.
-
- 16 9月, 2016 3 次提交
-
-
由 Sebastien Deleuze 提交于
Issue: SPR-14693
-
由 Sebastien Deleuze 提交于
Issue: SPR-14693
-
由 Brian Clozel 提交于
Since appcache manifests can have various file extensions, developers should register the (file extension, media type) mapping in their Spring MVC / Reactive Web configuration. This commit adds javadoc on both `AppCacheManifestTransformer` variants to explain how to do that. Issue: SPR-14510
-
- 14 9月, 2016 2 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-14521
-
由 Arjen Poutsma 提交于
Removed accidentally added ModelAndView class.
-
- 12 9月, 2016 5 次提交
-
-
由 Arjen Poutsma 提交于
In RoutingFunction, renamed 'and' to 'andSame', and 'andOther' to 'and' to make the commonly used method name shorter.
-
由 Arjen Poutsma 提交于
Merged all *Response implementations into one DefaultResponses class
-
由 Arjen Poutsma 提交于
This commit introduces template rendering support in the web.reactive package, through a Response.render method and a Rendering interface.
-
由 Sebastien Deleuze 提交于
Issue: SPR-14557
-
由 Sebastien Deleuze 提交于
Issue: SPR-14557
-
- 10 9月, 2016 2 次提交
-
-
由 Brian Clozel 提交于
This commit changes the default file extension configured with `AppCacheManifestTranformer`. This ResourceTransformer was previously considering `.manifest` files by default, but this has been changed in the official spec to `appcache`, in order not to clash with Microsoft's unregistered application/manifest type. Issue: SPR-14687
-
由 Brian Clozel 提交于
`ResolvedResource` is a rather generic name - changing the extended interface to something more meaningful: `HttpResource`. For now, implementations are linked with the resource handling chain, but this aspect has been removed from the interface documentation. Issue: SPR-14264
-
- 09 9月, 2016 4 次提交
-
-
由 Arjen Poutsma 提交于
Prior to this commit, FreeMarkerView used the system default charset to render. This commit switches this by defaulting to UTF-8, if no charset is specified in the content type. - Add contentType parameter to AbstractView.renderInternal, used to determine the charset contained therein - Adds a defaultCharset property to AbstractView and ViewResolverSupport.
-
由 Arjen Poutsma 提交于
Changed View's render method from taking a HandlerResult to taking a Map<String, ?>, in order to facilitate scenarios where a HandlerResult is not available (i.e. web.reactive.function).
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
- Changed Response.sse methods to allow for specific Publisher types to be returned in Response.
-
- 07 9月, 2016 3 次提交
-
-
由 Arjen Poutsma 提交于
Two changes to web.reactive.function: - Changed Response.stream method to allow for specific Publisher types to be returned in Response. - Router now stores HttpMessageReader|Writer retrieved from Configuration in the attributes as supplier, not as stream, to allow for multiple reads.
-
由 Arjen Poutsma 提交于
Removes attributes() method from Request, as it exposes a mutable map.
-
由 Brian Clozel 提交于
Prior to this commit, the resource handling chain and its `ResourceResolvers` would use specific `Resource` implementations in order to add resource metadata to the HTTP response. For example, `VersionedResource` and `EncodedResource` are both adding specific HTTP response headers. This commit aims at making this mechanism more stable and reusable, since the previous implementation would fail in case a resolved resource would be both a `VersionedResource` wrapping a `EncodedResource` (or the other way arount). Only one of the specific implementations would contribute its metadata since the code supporting that in `ResourceHttpRequestHandler` would only check for `instanceof` tests, whereas those implementations are acutally delegating calls to the wrapped resource. Now both `VersionedResource` and `EncodedResource` have been replaced by specific implementations of `ResolvedResource`, which directly provides those HTTP response headers as part of `getResponseHeaders()`. This commit applies the same changes for the web reactive implementations and its `ResourceWebHandler`. Issue: SPR-14264
-
- 06 9月, 2016 2 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-14521
-
由 Rossen Stoyanchev 提交于
A straight-forward port of the resource handling support in spring-webmvc to spring-web-reactive. Primarily adapting contracts and implementations to use the reactive request and response and the reactive ResourceHttpMessageWriter. Issue: SPR-14521
-
- 03 9月, 2016 1 次提交
-
-
由 Brian Clozel 提交于
This commit fixes `ResponseEntityResultHandler` so that it only tries to call `writeBody` if the `ResponseEntity` is not null. In case the response entity body is null, the response is flushed right away and the request is signaled as handled. Issue: SPR-14663
-
- 02 9月, 2016 3 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-14522
-
由 Rossen Stoyanchev 提交于
Issue: SPR-14522
-
由 Rossen Stoyanchev 提交于
Issue: SPR-14658
-
- 01 9月, 2016 2 次提交
-
-
由 Sebastien Deleuze 提交于
-
由 Arjen Poutsma 提交于
This commit introduces a new, functional web programming model in the org.springframework.web.reactive.function package. The key types are: - Request and Response are new Java 8-DSLs for access to the HTTP request and response - HandlerFunction represents a function to handle a request to a response - RoutingFunction maps a request to a HandlerFunction - FilterFunction filters a routing as defined by a RoutingFunction - RequestPredicate is used by Router to create RoutingFunctions - RequestPredicates offers common RequestPredicate instances
-