Deserialize error response without object mapper in WebClient onErrorResume

Question

I wonder if there is a better way to get error response in WebClient in a way that does not involve using additional ObjectMapper when calling onErrorResume?

In my WebClient:

import org.springframework.web.reactive.function.client.WebClientResponseException.BadRequest

// ...

.onErrorResume(BadRequest::class.java, badRequestToMyDto())

    private fun badRequestToMyDto(): (BadRequest) -> Mono<out MyDto> =
        { it: BadRequest ->
            val error = objectMapper.readValue<ErrorResponseDto>(it.responseBodyAsByteArray)
            // ...
}

There is a method .bodyToMono so I wonder if there is something similar that can be used in onErrorResume.

Consider using `exchangeToMono`. – lkatiforis Dec 11 '21 at 14:34 — lkatiforis, Dec 11 '21 at 14:34

score 3 · Accepted Answer · answered Dec 15 '21 at 17:20

You can use retrieve() in combination with onStatus to get access the client response when it is an "error". You can then invoke bodyToMono on it to unmarshall the response to a java object. Depending on the content type of the response body, spring will use the correct decoder. For examaple, if the body is json, it will use an ObjectMapper for unmarshalling.

WebClient.builder().build()
                .get()
                .uri("localhost:8080")
                .retrieve()
                .onStatus(HttpStatus::isError, clientResponse ->
                        clientResponse.bodyToMono(MyErrorResponse.class)
                                .flatMap(body -> {
                                    // logic
                                })
                )

and you can propagate deserialized response as mono? – pixel Dec 19 '21 at 07:25 — pixel, Dec 19 '21 at 07:25

Deserialize error response without object mapper in WebClient onErrorResume

1 Answers1