- 25 1月, 2019 2 次提交
-
-
由 Juergen Hoeller 提交于
Fixes #22307
-
由 Juergen Hoeller 提交于
Fixes #22306
-
- 24 1月, 2019 3 次提交
-
-
由 Arjen Poutsma 提交于
Fix Java 9 build by replacing deprecated method.
-
由 Juergen Hoeller 提交于
Fixes #22303
-
由 Juergen Hoeller 提交于
-
- 23 1月, 2019 1 次提交
-
-
由 Sam Brannen 提交于
Issue: #22288
-
- 22 1月, 2019 4 次提交
-
-
由 Rossen Stoyanchev 提交于
Fixes #22282
-
由 Rossen Stoyanchev 提交于
-
由 Brian Clozel 提交于
Prior to this commit, Spring WebFlux function would let `DecodingException` thrown by codecs bubble up to the web handler level. Since this exception is not handled by default there, the response would be turned into a HTTP 500 status. In the annotation model, `ArgumentResolver` implementations wrap this exception with a `ServerWebInputException`, which itself extends `ResponseStatusException`. The latter is supported by the error handling infrastructure as a HTTP 400 response. This commit ensures that `DecodingException` instances are properly wrapped in `ServerWebInputException` at the `ServerRequest` level directly, thus supporting all setup modes ("standalone" and through the `DispatcherHandler`). Fixes #22290
-
由 Sebastien Deleuze 提交于
This commit intends to clarify the documentation by avoiding confusion between @JsonView and Spring MVC JSON views. Fixes #22280
-
- 21 1月, 2019 2 次提交
-
-
由 Rossen Stoyanchev 提交于
Fixes #22287
-
由 Rossen Stoyanchev 提交于
Fixes #19841
-
- 19 1月, 2019 4 次提交
-
-
由 Rossen Stoyanchev 提交于
Fixes #22042
-
由 Rossen Stoyanchev 提交于
Fixes #22043
-
由 Rossen Stoyanchev 提交于
Fixes #22159
-
由 Rossen Stoyanchev 提交于
Fixes #22173
-
- 18 1月, 2019 6 次提交
-
-
由 Rossen Stoyanchev 提交于
Closes #22261
-
由 Rossen Stoyanchev 提交于
Fixes #22254
-
由 Sanghyuk Jung 提交于
-
由 Rossen Stoyanchev 提交于
Fixes #22269
-
由 Rossen Stoyanchev 提交于
Fixes #22270
-
由 Brian Clozel 提交于
Prior to this commit, `DataBuffer.write` would throw an `IllegalStateException` when called with an empty `String`, since the `CharsetEncoder` would be flushed on an incorrent state. This commit skips entirely the encoding phase for empty `String`. Fixes #22262
-
- 14 1月, 2019 1 次提交
-
-
由 Arjen Poutsma 提交于
Resolves #22249
-
- 09 1月, 2019 15 次提交
-
-
由 Sam Brannen 提交于
Issue: SPR-17647
-
由 Sam Brannen 提交于
Issue: SPR-17654
-
由 Sam Brannen 提交于
-
由 Spring Buildmaster 提交于
-
由 Juergen Hoeller 提交于
-
由 Rossen Stoyanchev 提交于
Issue: SPR-17630
-
由 Juergen Hoeller 提交于
-
由 Andrzej Leśkiewicz 提交于
Correct handling of not/and expressions in ProfilesParser Issue: SPR-17606
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Sam Brannen 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
This allows for proper nested type conversion in @Value Optional fields analogous to method parameters, through a new TypeDescriptor-based method in the TypeConverter SPI. As an additional and less involved measure that is worth backporting, DefaultListableBeanFactory defensively checks for pre-converted Optional wrappers. Issue: SPR-17607
-
由 Juergen Hoeller 提交于
Issue: SPR-17645
-
由 Rossen Stoyanchev 提交于
Commit #93b7a4 added support for pre-configuring URI variables at the UriComponentsBuilder level, and also changed toUriString to encode template and URI variables separately. However this went a bit too far causing side effects for URLs with curly braces that don't represent URI variables. This commit restores the original toUriString behavior which is to encode template and URI variables sepraately only if URI variables have been pre-configured. Issue: SPR-17630
-
- 08 1月, 2019 2 次提交
-
-
由 Sam Brannen 提交于
For details, see: https://github.com/junit-team/junit4/issues/1585
-
由 Sam Brannen 提交于
-