- 18 12月, 2016 1 次提交
-
-
由 Juergen Hoeller 提交于
Includes consistent use of ResolvableType.resolve() wherever applicable. Issue: SPR-15011
-
- 17 12月, 2016 7 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-14978
-
由 Rossen Stoyanchev 提交于
Apply the new HttpHeaders#getAcceptLanguageAsLocale() in places where it was hardcoded or defaulting. Apply ServerHttpResponse.encodeUrl in RequestContext. Issue: SPR-15024
-
由 Rossen Stoyanchev 提交于
An update on the last commit switching from: List<Locale> getAcceptLanguageAsLocales() to Locale getAcceptLanguageAsLocale() This best supports the scenario for the most preferred Locale. If there is a need to look at the prioritized list of languages it's best to use Locale.filter with the LocaleRange's. This is explained in the Javadoc for getAcceptLanguage(). Issue: SPR-15024
-
由 Rossen Stoyanchev 提交于
The use of Locale.LanguageRange for the Accept-Language header makes sense as it gives the most flexibility for a client to set a weighted list and for a server to do filtering via Locale#filter. This commit adds an additional convenience method that turns the LangugeRange list to a list of Locale's also filtering out a wildcard (i.e. "*"). A List<Locale> is the most basic way to access prefered languages and needed when filtering is not required. Issue: SPR-15024
-
由 Rossen Stoyanchev 提交于
-
由 Stephane Maldini 提交于
-
- 16 12月, 2016 6 次提交
-
-
由 Rossen Stoyanchev 提交于
Consolidate into one method potentially re-using UriComponentsBuilder for the location. Also use StringUtils#applyRelativePath. Issue: SPR-15020
-
由 Rob Winch 提交于
Previously ForwrdedHeaderFilter did not ensure that HttpServletResponse.sendRedirect worked properly based on X-Forwarded-* headers. This commit updates ForwardedHeaderFilter to overrided the HttpServletResponse.sendRedirect method to ensure X-Forwarded-* headers are honored. Issue SPR-15020
-
由 Rossen Stoyanchev 提交于
ServerWebExchange.Builder has an additional Consumer-style shortcut method that accepts a builder for modifying the request. ServerWebExchange and ServerHttpRequest builders have fewer methods, more use-case focused vs matching directly to properties.
-
由 Rossen Stoyanchev 提交于
ServerWebExchange now provides access to "requestParams" as a MulitValueMap with query parameters and form data combined. The combined map is then used for the params condition of @RequestMapping purposes () and also for @RequestParam arguments. Issue: SPR-15000
-
由 Sebastien Deleuze 提交于
Issue: SPR-14536
-
由 Sebastien Deleuze 提交于
Issue: SPR-15024
-
- 15 12月, 2016 22 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-14978
-
由 Juergen Hoeller 提交于
Issue: SPR-15017
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
-
由 Sebastien Deleuze 提交于
Issue: SPR-14992
-
由 Stephane Maldini 提交于
-
由 Rossen Stoyanchev 提交于
Renamed: AbstractListenerFlushProcessor -> AbstractListenerWriteFlushProcessor
-
由 Rossen Stoyanchev 提交于
This is similar to the WriteListener changes on the ServerHttpResponse where we are more naturally exposed to a delayed write. Nevertheless we could also have a delayed read and should be consistent. The early initialization of the RequestBodyPublisher also simplifies the internal implementation a bit.
-
由 Juergen Hoeller 提交于
Issue: SPR-15019
-
由 Juergen Hoeller 提交于
Issue: SPR-15015
-
由 Juergen Hoeller 提交于
Issue: SPR-15010
-
由 Juergen Hoeller 提交于
Issue: SPR-15009
-
由 Juergen Hoeller 提交于
Issue: SPR-14527
-
由 Rossen Stoyanchev 提交于
Instead of registering an AsyncListener in ServletHttpHandlerAdapter we now register an AsyncListener in each of the request and response where the events need to be handled anyway. This allows removing the package private delegation methods in the request and response.
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
The Undertow HttpServerExchange has a complete listener which we can use instead of the close() method UndertowServerHttpRequest.
-
由 Violeta Georgieva 提交于
- lazy allocate the PooledByteBuffer, only if there is a request body for reading - close the PooledByteBuffer once the request finishes
-
由 Juergen Hoeller 提交于
SPR-15018 - Construct RowMapper using the impl hook
-
- 14 12月, 2016 4 次提交
-
-
由 Arjen Poutsma 提交于
This commit makes it possible for handler functions to return asynchronous status codes and headers, by making HandlerFunction.handle return a Mono<ServerResponse> instead of a ServerResponse. As a consequence, all other types that deal with HandlerFunctions (RouterFunction, HandlerFilterFunction, etc.) had to change as well. However, when combining the above change with method references (a very typical use case), resulting signatures would have been something like: ``` public Mono<ServerResponse<Mono<Person>>> getPerson(ServerRequest request) ``` which was too ugly to consider, especially the two uses of Mono. It was considered to merge ServerResponse with the last Mono, essentialy making ServerResponse always contain a Publisher, but this had unfortunate consequences in view rendering. It was therefore decided to drop the parameterization of ServerResponse, as the only usage of the extra type information was to manipulate the response objects in a filter. Even before the above change this was suggested; it just made the change even more necessary. As a consequence, `BodyInserter` could be turned into a real `FunctionalInterface`, which resulted in changes in ClientRequest. We did, however, make HandlerFunction.handle return a `Mono<? extends ServerResponse>`, adding little complexity, but allowing for future `ServerResponse` subtypes that do expose type information, if it's needed. For instance, a RenderingResponse could expose the view name and model. Issue: SPR-14870
-
由 mmoores 提交于
Call getColumnRowMapper() to create the row mapper; prevents requirement to override extractReturnedResults().
-
由 Sebastien Deleuze 提交于
Issue: SPR-15013
-
由 Rossen Stoyanchev 提交于
We no longer should need the workaround for: https://github.com/reactor/reactor-netty/issues/2 Issue: SPR-14643
-