- 19 11月, 2019 1 次提交
-
-
由 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
-
- 13 11月, 2019 2 次提交
-
-
由 Rossen Stoyanchev 提交于
See gh-1956
-
由 jerzykrlk 提交于
-
- 11 11月, 2019 2 次提交
-
-
由 Juergen Hoeller 提交于
Closes gh-23976
-
由 Rossen Stoyanchev 提交于
Closes gh-23409
-
- 08 11月, 2019 2 次提交
-
-
由 Rossen Stoyanchev 提交于
Apply default Accept header for HttpUrlConnection only. See gh-23855
-
由 Lorenzo Torracchi 提交于
Closes gh-23740
-
- 06 11月, 2019 1 次提交
-
-
由 Sam Brannen 提交于
See gh-23939
-
- 30 10月, 2019 2 次提交
-
-
由 Rossen Stoyanchev 提交于
See gh-23741
-
由 Rossen Stoyanchev 提交于
A ResponseStatus exception now exposes extra method to return headers for the response. This is used in ResponseStatusExceptionHandler to apply the headers to the response. Closes gh-23741
-
- 25 10月, 2019 2 次提交
-
-
由 Rossen Stoyanchev 提交于
Closes gh-23780
-
由 Rossen Stoyanchev 提交于
See gh-23803
-
- 24 10月, 2019 1 次提交
-
-
由 Rossen Stoyanchev 提交于
See gh-23780
-
- 23 10月, 2019 3 次提交
-
-
由 Johnny Lim 提交于
-
由 Rossen Stoyanchev 提交于
See gh-23764
-
由 Rossen Stoyanchev 提交于
Closes gh-23764
-
- 27 9月, 2019 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 26 9月, 2019 1 次提交
-
-
由 Sam Brannen 提交于
See gh-23638
-
- 24 9月, 2019 1 次提交
-
-
由 Rossen Stoyanchev 提交于
If an error looks like a "disconnected client" but the response is not yet committed then it can't be an I/O error from writing to the server response. It is most likely as a result of a remote call as part of request handling. Not setting the response to 500 in this case results in a 200 response status despite the error. Even if it was an I/O error from the server response, setting the status won't impact a failed response. Closes gh-23319
-
- 16 9月, 2019 2 次提交
-
-
由 Phillip Webb 提交于
See gh-23539 Co-authored-by: NSam Brannen <sbrannen@pivotal.io>
-
由 Napster 提交于
Closes gh-23567
-
- 12 9月, 2019 1 次提交
-
-
由 Rossen Stoyanchev 提交于
Closes: gh-23596
-
- 05 9月, 2019 1 次提交
-
-
由 Phillip Webb 提交于
See gh-23539
-
- 28 8月, 2019 1 次提交
-
-
由 Сергей Цыпанов 提交于
Closes gh-23470
-
- 23 8月, 2019 1 次提交
-
-
由 Sam Brannen 提交于
-
- 21 8月, 2019 1 次提交
-
-
由 Rossen Stoyanchev 提交于
Closes gh-23490
-
- 17 8月, 2019 1 次提交
-
-
由 Sam Brannen 提交于
-
- 01 8月, 2019 3 次提交
-
-
由 Phillip Webb 提交于
Deprecate all mutation methods in `MethodParameter` in favor of factory methods that return a new instance. Existing code that previously relied on mutation has been updated to use the replacement methods. Closes gh-23385
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
- 30 7月, 2019 2 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Rossen Stoyanchev 提交于
The isJavaIdentifier check is not really required, but also seems intuitive for variables to be Java identifier-like. This commit relaxes the constraint a bit by also allowing "-". Closes gh-23101
-
- 22 7月, 2019 1 次提交
-
-
由 Rossen Stoyanchev 提交于
To make the switching of separators complete, it is also important to know whether the decoding of path segment values and the parsing of path param should be done as those are applied transparently. This commit replaces the recently added separator argument to PathContainer.parsePath with an Options type with two predefined constants. One for HTTP URLs with automatic decoding and parsing of path params, and another for "." separated message routes without decoding except for encoded sequences of the separator itself. See gh-23310
-
- 19 7月, 2019 3 次提交
-
-
由 Rossen Stoyanchev 提交于
-
由 Andreas Kluth 提交于
-
由 Rossen Stoyanchev 提交于
Replace docs on using MultipartBodyBuilder for the RestTemplate with examples that show MultiValueMap. Originally the idea was to make MultipartBodyBuilder accessible to the RestTemplate too, but with support for async parts that's no longer a good fit. Closes gh-23295
-
- 18 7月, 2019 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 15 7月, 2019 1 次提交
-
-
由 Rossen Stoyanchev 提交于
OncePerRequestFilter now has a doFilter method that allows separate processing of nested ERROR dispatches. This is useful for filters that wrap the request and response. Closes gh-23196
-
- 11 7月, 2019 1 次提交
-
-
由 桂坤 提交于
See gh-23274
-
- 10 7月, 2019 1 次提交
-
-
由 Arjen Poutsma 提交于
Revert to state before DefaultMultipartMessageReader
-