Please forgive my ignorance and lack of library knowledge, but: My concern is related to how the *missing* properties are mapped to null by default.
Wouldn't be a good idea to have the @JsonSetter annotation handle the properties classified as missing in a similar fashion as the nulls are handled? I mean, it would be handy to have the possibility to say @JsonSetter(missing=Missings.SKIP) or @JsonSetter(missing=Missings.AS_EMPTY). This is useful in the context of explicitly setting a property to null or implicitly on missing, leaving the developer with some space of maneuver in regards to the deserialization process. If there are other means to achieve this functionality, I'd be grateful to know how to use. Thank you, Alex -- You received this message because you are subscribed to the Google Groups "jackson-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
