FAIL_ON_NULL_FOR_PRIMITIVES failure does not indicate field name in exception message

[raderio]

public class Test {

    private String type;
    private long num;

    @JsonCreator
    public Test(@JsonProperty(value = "type", required = true) String type,
                @JsonProperty(value = "num", required = true) long num) {
        this.type = type;
        this.num = num;
    }

    public String getType() {
        return type;
    }

    public void setType(String type) {
        this.type = type;
    }

    public long getNum() {
        return num;
    }

    public void setNum(long num) {
        this.num = num;
    }
}

ObjectMapper objectMapper = new ObjectMapper();
        objectMapper.configure(DeserializationFeature.FAIL_ON_NULL_FOR_PRIMITIVES, true);

        try {
            String json = "{ \"type\" : \"number\", \"num\":null }";
            Test car = objectMapper.readValue(json, Test.class);

            System.out.println(car.getNum());
        } catch (MismatchedInputException ex) {
            ex.getPath().forEach(it -> System.out.println("field: " + it.getFieldName()));
        }

shows field: num
but missing field in json

ObjectMapper objectMapper = new ObjectMapper();
        objectMapper.configure(DeserializationFeature.FAIL_ON_NULL_FOR_PRIMITIVES, true);

        try {
            String json = "{ \"type\" : \"number\" }";
            Test car = objectMapper.readValue(json, Test.class);

            System.out.println(car.getNum());
        } catch (MismatchedInputException ex) {
            ex.getPath().forEach(it -> System.out.println("field: " + it.getFieldName()));
        }

shows nothing

Please add filed name and in this case.

[cowtowncoder]

Thank you for reporting the issue: it does look like a bug.

[cowtowncoder]

Actually, I was wrong: it is not a bug -- path refers to logical context within JSON content, and there is no property in latter case that triggers the exception: it is the lack of content that triggers it.
While information on missing logical property (distinct from JSON property in input) would be useful, that is not what path reference tracks.

[raderio]

While information on missing logical property (distinct from JSON property in input) would be useful

Can you please than add a new property which will hold the name? It will be really useful when to send a response to client, and indicate what fields has errors.

[cowtowncoder]

@raderio Actually, come to think of it bit more, I wonder if I was wrong. Reference mentions "field" or "key", in Java context, and not in input source.

I'll have to think bit more about this after all, since that being the case, it is not unreasonable it would be populated if there is sufficient information to do so.

[raderio]

Thanks.

[neetkee]

We have a similar problem. It would be great to have the same behavior with fields of different types.

[cowtowncoder]

@neetkee Agreed. At this point it would be necessary to find someone with time to work on this, however.

[WellingR]

I also encountered this issue and wanted to report this. I have a potential fix ready and will create a PR soon