- 12 8月, 2016 3 次提交
-
-
由 Juergen Hoeller 提交于
(cherry picked from commit a4a71a89)
-
由 Juergen Hoeller 提交于
Issue: SPR-14551
-
由 Juergen Hoeller 提交于
PersistenceAnnotationBeanPostProcessor obtains default EntityManagerFactory via getBean(Class) algorithm Issue: SPR-7549
-
- 10 8月, 2016 8 次提交
-
-
由 Juergen Hoeller 提交于
(cherry picked from commit 35e247aa)
-
由 Stephane Nicoll 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Stephane Nicoll 提交于
* pr/1129: Fix typo
-
由 wolverine.kim 提交于
Closes gh-1129
-
由 Juergen Hoeller 提交于
Issue: SPR-14554
-
由 Sebastien Deleuze 提交于
-
- 09 8月, 2016 5 次提交
-
-
由 Juergen Hoeller 提交于
(cherry picked from commit aade2d1e)
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-14563
-
由 Rossen Stoyanchev 提交于
Issue: SPR-14565
-
由 Rossen Stoyanchev 提交于
-
- 08 8月, 2016 6 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-14548
-
由 Juergen Hoeller 提交于
Issue: SPR-14549
-
由 Juergen Hoeller 提交于
Issue: SPR-14550
-
由 Juergen Hoeller 提交于
Issue: SPR-14561
-
由 Sebastien Deleuze 提交于
reactor.test.TestSubscriber will not be part of Reactor Core 3.0.0 since it needs to be refactored to fit all the needs expressed by the users. It is likely to be back later in one of the Reactor Core 3.0.x releases. This commit anticipate this removal by temporarily copying TestSubscriber in spring-core test classes. As soon as the new TestSubscriber will be available in Reactor Core, Spring Framework reactive tests will use it again.
-
- 06 8月, 2016 2 次提交
-
-
由 Stephane Nicoll 提交于
-
由 Stephane Nicoll 提交于
Issue: SPR-14552
-
- 05 8月, 2016 1 次提交
-
-
由 Sebastien Deleuze 提交于
Issue: SPR-14520
-
- 04 8月, 2016 3 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-14548
-
由 Juergen Hoeller 提交于
-
由 Arjen Poutsma 提交于
-
- 03 8月, 2016 1 次提交
-
-
由 Brian Clozel 提交于
-
- 30 7月, 2016 2 次提交
-
-
由 Stephane Nicoll 提交于
* pr/1126: Use abbreviated expression lambda instead of statement lambda
-
由 Kamil Szymanski 提交于
Closes gh-1126
-
- 28 7月, 2016 9 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-14328
-
由 Juergen Hoeller 提交于
Issue: SPR-13826
-
由 Juergen Hoeller 提交于
Issue: SPR-14517
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
There is really no need for a result handler dedicated to a void return value and it's actually problematic to have it. Each result handler treats void as necessary. For an @ResponseBody method it means an empty body. For view resolution it means no specific value was returned and we should procede with selecting a default view name. Having a dedicated void result handler can interfere with this especially since view resolution needs to be last in order. At the same time there are cases when no result handling is needed and the response is fully handled within the HandlerAdapter. This is the case with WebHandler and the SimpleHandlerAdapter. For that case we simply return mono.then(aVoid -> Mono.empty()) which effectively returns an empty Mono and no result handling follows. The HandlerAdapter already says you can return no values at all if the response is fully handled.
-
由 Juergen Hoeller 提交于
JndiPropertySource defensively skips invalid JNDI lookup for property name with colon in resource-ref mode Issue: SPR-14518
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-