Jackson: custom ObjectMapper not delegated to MicroProfile RestClient

[nimo23]

Describe the bug

I customized the Quarkus Jackson Object Mapper:

@Singleton
@JBossLog
public class MyMapper implements ObjectMapperCustomizer {

	public void customize(ObjectMapper mapper) {
            mapper.disable(DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES);
	}

}

According to #12104 (comment), the

RestClientBuilder.newBuilder() or QuarkusRestClientBuilder.newBuilder() (I tried both) should use my customized ObjectMapper. However, this is not the case as I get the exception:

com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: 
Unrecognized field "password" (class app.User), not marked as ignorable (one known property: "name"])

Expected behavior

My custom "Quarkus Jackson Object Mapper" should be delegated to RestClient when built using RestClientBuilder.newBuilder() or QuarkusRestClientBuilder.newBuilder().

Actual behavior

My custom "Quarkus Jackson Object Mapper" is not delegated to RestClient when built using RestClientBuilder.newBuilder() or QuarkusRestClientBuilder.newBuilder().

How to Reproduce?

1. Customize Jackson Object Mapper (e.g. to use disable FAIL_ON_UNKNOWN_PROPERTIES)
2. Build RestClient by using (a) RestClientBuilder.newBuilder() and (b) QuarkusRestClientBuilder.newBuilder().
3. Make a Client GET-Request from a java record such as:
   public record User(@JsonProperty("name") String name) {}
4. You will see, that the custom Jackson mapper is not used for the RestClient.

Output of uname -a or ver

No response

Output of java -version

openjdk version "21.0.2" 2024-01-16

Quarkus version or git rev

3.9.2

Build tool (ie. output of mvnw --version or gradlew --version)

maven

Additional information

No response

[quarkus-bot]

/cc @geoand (jackson), @gsmet (jackson)

[geoand]

This is interesting indeed. Can you attach a sample application that behaves as you describe so we can dig into it?

Thanks

[geoand]

I would also like you know which REST Client extension you are using

[nimo23]

I use the the following quarkus 3.9.2 dependencies:

• quarkus-rest-jackson
• quarkus-rest-client-jackson

from my pom.xml:

..
<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-rest-jackson</artifactId>
</dependency>
<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-rest-client-jackson</artifactId>
</dependency>

With the above dependency, the Microprofile Rest Client-extension (microprofile-rest-client-api-3.0.1.jar) is used.

[geoand]

Okay, please attach a sample application in that case so I can try it out.

[nimo23]

I found the reason when creating the reproducer. It was my fault, I had accidentally used another default mapper (with mapper.enable(DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES)) instead of using the Quarkus managed mapper. Using the quarkus managed mapper solves this issue.

So there is no bug here.

[geoand]

Thanks for the update