Brian Clozel 58f58e404e Avoid null signals when resolving handler arguments ...

Prior to this commit, resolving an argument for a WebFlux controller
that's missing from the request and not required by the handler would
throw a NullPointerException in some cases.

This involves the conversion of the parameter (a `String` parameter type
might not trigger this behavior) and sending a `null` within a reactive
stream, which is illegal per the RS spec.

We now rely on a `Mono.justOrEmpty()` to handle those specific cases.

Issue: SPR-17050
(Cherry-picked from a7f97a1669)

2018-07-18 14:48:06 +02:00

..

src

Avoid null signals when resolving handler arguments

2018-07-18 14:48:06 +02:00

spring-webflux.gradle

Remove dependency management noise from POMs

2018-06-11 16:02:11 +02:00