WebFluxMessageHandlerSpec should support chaining

[asarkar]

WebFluxMessageHandlerSpec.replyPayloadToFlux

The workaround is to create a method like the following:

private WebFluxMessageHandlerSpec webFluxMessageHandlerSpec() {
    WebFluxMessageHandlerSpec spec = WebFlux.outboundGateway(m -> m.getPayload().toString(), webClient)
            .expectedResponseType(Whatever.class)
            .httpMethod(GET)
            .mappedRequestHeaders(ACCEPT);
    spec.replyPayloadToFlux(true);

    return spec;
}

@artembilan this is what we discussed on Twitter. Since I don't see the fix yet in the repo, I'm going to proceed with a PR myself.

[artembilan]

@asarkar ,

sorry, was side-tracked with other urgent stuff.

Yes, the workaround is correct. That definitely doesn't matter if we don't provide method chain support the things are not going to work.

Please, proceed with the PR and also consider to fix similar problem for the bodyExtractor() hook as well.

Thank you!

[asarkar]

Just made the PR (as indicated above by GH). Regarding bodyExtractor, you means the following should be changed too?

public void bodyExtractor(BodyExtractor<?, ClientHttpResponse> bodyExtractor) {
    this.target.setBodyExtractor(bodyExtractor);
}

[artembilan]

Right, that one should follow method chain design as well.
Thanks, I see a PR.

[asarkar]

Just updated it with the bodyExtractor. Now it has both fixes.