ResponseEntity<Single<>> instead of Single<ResponseEntity<>>

The new code introduced here allows the controller to return Single or Observable.

Although it has some flaws handling the http status code.

1. It does not honor @ResponseStatus annotations on the controller itself.
2. It does support ResponseEntity<Single<>> which is useless in any case where the status code depends on the reactive code, for instance: it is impossible to write a proper ResponseEntity<Single<User>> findUser() method as it will necessarily subscribe and consume the Single at the controller instead of at the response handler.
3. It doesn’t implement support for Completable.

[rstoyanchev]

Indeed it looks like there is no way to vary the status based on the outcome. In other words it should deal with Single<ResponseEntity<>>.

Not sure what’s the issue with @ResponseStatus. That should be set regardless of the return value handler used. Perhaps it’s getting overridden later when the Single completes?

[spencergibb]

now 1.2.0.RELEASE