@JsonIgnoreProperties ignoreUnknown does not work with @JsonDeserialize builder

Trying to unmarshall an object like:

@JsonDeserialize(builder = TestObject.Builder.class)
@JsonIgnoreProperties(ignoreUnknown = true)
public class TestObject {

    private final String property1;

    private TestObject(Builder builder) {
        property1 = builder.property1;
    }

    public static Builder builder() {
        return new Builder();
    }

    public String getProperty1() {
        return property1;
    }

    public static class Builder {

        private String property1;

        public Builder withProperty1(String property1) {
            this.property1 = property1;
            return this;
        }

        public TestObject build() {
            return new TestObject(this);
        }

    }
}

from a String like:

{"property1":"value1", "property2":"value2"}

causes UnrecognizedPropertyException.

The same String when unmarshalled to

@JsonIgnoreProperties(ignoreUnknown = true)
public class TestObjectNoBuilder {

    private String property1;

    public String getProperty1() {
        return property1;
    }

    public void setProperty1(String property1) {
        this.property1 = property1;
    }

}

works as expected - there’s no exception for property2.

Tested with Jackson 2.6.5 and 2.7.3. Might be similar to https://github.com/FasterXML/jackson-databind/issues/1118.

[ChrisRenke]

I recently ran into this general issue in conjunction with the Lombok library, which generates builders with a single annotation. Sadly, I cannot seem to figure out a workaround as it is not currently possible with Lombok to add annotations to its generated builder classes, and thus I cannot give the builder a @JsonIgnoreProperties(ignoreUnknown = true) annotation. If I replace the generated Lombok builder with a hand-rolled identical builder and give annotate the builder class with @JsonIgnoreProperties(ignoreUnknown = true), everything functions correctly.

The reasoning for closing the issue seems sound, though I did want to leave this breadcrumb in case anyone’s searching for answers in the same state as me and ends up here. I’m going to go to the lombok project and propose being able to append annotations to the generated builders, as it both solves the issue at hand with Jackson and extends an existing Lombok paradigm.

[cowtowncoder]

@ChrisRenke Thank you for sharing this. Depending on how collaboration with Lombok team goes, I am open to considering this problem, and it may make sense to file a new issue focused specifically around case of builders generated by packages like Lombok (auto-values, immutables; there seem to be a few around).