Thanks, Tatu. Is there any existing discussion around introducing this as a
feature? Missing and null properties are very different from a protocol
point of view, not honouring the distinction seems like a big oversight.
On Tuesday, 6 March 2018 03:16:42 UTC, Tatu Saloranta wrote:
> > For bean setters we have
> > https://github.com/FasterXML/jackson-databind/issues/1402, which AFAICT
> > allows to specify different behaviour for nulls vs missing keys.
> > I want to achieve the same but also preserve immutability (and sanity).
> > What's the simplest way of doing that? Sniffing around the code base I
> > `PropertyValueBuffer._findMissing` just uses the deserializer's null
> > and I don't understand Jackson's extension points well.
> > In my case I'm using Java 8/9 Optionals and the observed behaviour is as
> > follows:
> > - Field has a value: I get Optional.of(value)
> > - Field is null: I get Optional.empty()
> > - Field key is missing: I get Optional.empty()
> > How do I distinguish between case 2 and 3?
> You can not distinguish them. You can get an exception, if you want,
> by marking specific property/-ies
> passed as required (@JsonProperty(required=true)), but that's it.
> -+ Tatu +-
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to email@example.com.
For more options, visit https://groups.google.com/d/optout.