- 23 3月, 2018 2 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Aligned with DataBindingPropertyAccessor and shown in ref doc examples. Issue: SPR-16588
-
- 22 3月, 2018 7 次提交
-
-
由 Rossen Stoyanchev 提交于
-
由 sn42 提交于
-
由 Christoph Dreis 提交于
Use Collection.removeIf() where possible Issue: SPR-16622
-
由 Rossen Stoyanchev 提交于
Rather than create a new EvaluationContext instance per evaluation, we now create a statically shared instance, without the root object in it, and re-use it for all evalutations.
-
由 Rossen Stoyanchev 提交于
Issue: SPR-16588
-
由 Juergen Hoeller 提交于
Includes configurable write support at ReflectivePropertyAccessor level. Issue: SPR-16588
-
由 Rossen Stoyanchev 提交于
-
- 21 3月, 2018 7 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
The web.server package is quite low-level and should not depend on web.bind in order to avoid a dependency cycle. Extracting the introspection of the ResponseStatus annotation into a WebFlux-level subclass resolves the cycle. Issue: SPR-16567
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-16588
-
由 Juergen Hoeller 提交于
Issue: SPR-16616
-
由 Rossen Stoyanchev 提交于
Undertow does not provide a way to check if data is available to read but instead we have to try to read and see if any data is returned. This makes it impossible to implement checkOnDataAvailable without trying to read and that can lead to infinite recursion like this: ... UndertowServerHttpRequest$RequestBodyPublisher.checkOnDataAvailable(UndertowServerHttpRequest.java:156) AbstractListenerReadPublisher.changeToDemandState(AbstractListenerReadPublisher.java:177) AbstractListenerReadPublisher.access$900(AbstractListenerReadPublisher.java:47) AbstractListenerReadPublisher$State$4.onDataAvailable(AbstractListenerReadPublisher.java:319) AbstractListenerReadPublisher.onDataAvailable(AbstractListenerReadPublisher.java:85) UndertowServerHttpRequest$RequestBodyPublisher.checkOnDataAvailable(UndertowServerHttpRequest.java:156) This commit prevent the call to checkOnDataAvailable() when switching states from READING->DEMAND which implies we exited the readAndPublish loop because there was no more data to read. Issue: SPR-16545
-
由 Rossen Stoyanchev 提交于
Issue: SPR-12452
-
- 20 3月, 2018 4 次提交
-
-
由 Rossen Stoyanchev 提交于
Most Servlet containers do this anyway, but not all, and not consistently for forward and backslashes. Issue: SPR-16616
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-7885
-
由 Rossen Stoyanchev 提交于
-
- 19 3月, 2018 8 次提交
-
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
Issue: SPR-16608
-
由 Juergen Hoeller 提交于
Issue: SPR-16607
-
由 Juergen Hoeller 提交于
Issue: SPR-16612
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-16611
-
由 Juergen Hoeller 提交于
Issue: SPR-16607
-
- 18 3月, 2018 1 次提交
-
-
由 Wang Jingyu 提交于
* Fix AsciiDoc typos in AOP documentation * Polish formatting
-
- 17 3月, 2018 7 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-16606
-
由 Rossen Stoyanchev 提交于
Issue: SPR-16601
-
由 Rossen Stoyanchev 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-16602
-
由 Arjen Poutsma 提交于
The former method clashed with the ClientRequest.method() getter.
-
由 Arjen Poutsma 提交于
This commit introduces ClientResponse.Builder, an easier way to create a ClientResponse from an existing response, or from scratch. Issue: SPR-16553
-
- 16 3月, 2018 4 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-16599
-
由 Rossen Stoyanchev 提交于
Issue: SPR-16591
-
由 Rossen Stoyanchev 提交于
Issue: SPR-16597
-
由 Rossen Stoyanchev 提交于
Issue: SPR-14694
-