'Different ObjectMapper / ObjectMapperCustomizer for client and service implementations

Quarkus allows a program to use specify a custom Jackson ObjectMapper by using CDI producer method or customize the ObjectMapper with ObjectMapperCustomizer instances.

I need to have different behaviors for RestEasy Reactive Client use and RestEasy Reactive use. Specifically, I want the service implementation to be set with .configure(DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES, true) and the client to have .configure(DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES, false)

Is it possible to achieve this in Quarkus version 2.7.1.Final?

quarkusresteasyreactive


Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source

Related Questions

Quarkus No serializer found class io.smallrye.mutiny.operators.uni.builders.UniCreateFromPublisher no properties discovered to create BeanSerializer

Why am i getting timeout exception after 4 requests to database?

spring reactive retry with exponential backoff conditionally

404 error with swagger-ui and spring webflux

Reactive bar chart in shiny R

Trouble binding ViewModel to View, as part of a ListViewItem DataTemplate with ReactiveUI

Props gotten directly from vue 3 setup are not reactive

Svelte reactive statement with a variable fron onMount

How to receive a type from Angular 12 reactive dropdown list when change fired

WebFlux Spring Boot @Transactional with reactive MongoDB

How to return a reactive dataframe from within a shiny module that depends on a button click?

return Mono.error inside Map Spring Webflux

Java Spring Reactive, returning one Mono<..> from many multiple requests

resteasy-cdi breaks deployment to Tomcat 7

Inject HttpServerRequest in service via Quarkus