Disabling SerializationFeature.FAIL_ON_EMPTY_BEANS does not affect canSerialize

[nickwongdev]

Spring's REST Template calls this method on MappingJackson2HttpMessageConverter:

public boolean canWrite(Class<?> clazz, MediaType mediaType) {
    return (this.objectMapper.canSerialize(clazz) && canWrite(mediaType));
}

However, this fails even though I have set:

converter.getObjectMapper().disable(SerializationFeature.FAIL_ON_EMPTY_BEANS);

And, in fact, it will serialize the payload just fine, even though it reports that it cannot:

System.out.println(converter.getObjectMapper().canSerialize(EmptyModel.class));
System.out.println(converter.getObjectMapper().writeValueAsString(em));
System.out.println(converter.getObjectMapper().canSerialize(EmptyModel.class));

false
{}
false

Also, related to bug #703 , with version 2.5.1, the result is:

false
{}
true

I haven't had time to trace down what is enabling the actual serialization to go through on writeValueAsString, but I can try to comment later on this.

[cowtowncoder]

Thank you for reporting this: it does sound like a bug indeed. As #703, that should be fixed in 2.5.2 that has been released.

[cowtowncoder]

Fix turned out to be bit more involved than I thought, so it will only go in 2.6.0, to minimize risk of regression in a patch release.

[nickwongdev]

Thanks! 👯