How do I handle WebClient exceptions when using block()?

Question

I have a service written using spring web. However, to perform our http calls we have decided to use WebClient (I do not have the option to use RestTemplate or convert the service to use WebFlux). So, in the block code below:

public List<SomeObject> getObject(final String param1, final String param2) {
        return openApiGenerateClient.getSomething(param1, param2)
                .collectList()
                .onErrorResume(WebClientResponseException.BadRequest.class, t -> error(new CustomException(t)))
                .block();
    }

I have a client side code generated by openApi which uses WebClient to perform the http request. The response is a Flux. I would like to "catch" specific errors, such as "Bad Request" and convert into my custom error to be handled in my Controller Advice. This code above although it compiles, when tested always return the exception of type WebClientResponseException.BadRequest and not my CustomException.

I have tried other Flux operations such as .onErrorReturn . I know I can simply wrap my call in a try and catch and then handle the errors, but I would like to know if there is a cleaner way of doing, without having some ugly code with multiple catchs.

Did you read the official docs for wwbflux, because it is described there — Toerktumlare, Feb 14 '23 at 01:02

score 0 · Answer 1 · edited Feb 23 '23 at 16:08

I didn't test it but it seems that it should catch the errors before doing the collectList.

    public List<SomeObject> getObject(final String param1, final String param2) {
        return openApiGenerateClient.getSomething(param1, param2)
                .onErrorResume(WebClientResponseException.BadRequest.class, t -> error(new CustomException(t)))
                .collectList()
                .block();
    }

By doing this you expect the error to be throwed by the getSomething call, instead of expecting it in the collectList().

How do I handle WebClient exceptions when using block()?

1 Answers1