There is no support for such variations at this point. I suspect most users would first bind JSON into Map or JsonNode, manipulate it into some sort of canonical representation, then use databinding.
-+ Tatu +- On Tue, Aug 23, 2016 at 9:11 AM, JP <[email protected]> wrote: > Hi all, > > Is there an eloquent way to handle the scenario where the JSON string > field names may be changing (depending on environment)? > > In development environment: > { "id" : 1234, "name1" : "John" } > > In production environment: > { "id" : 1234, "name2" : "John" } > > What I really want is the ability to do this to my POJO object: > > @JsonProperty("${env.nameField}") > private String name; > > Basically, a way to externalize the @JsonProperty annotation configuration > in a properties file so that it's controlled by the respective deployment > packaging. > > However, since the above is not possible, what is the next best way to > handle this scenario? > > Thanks! > jp > > -- > You received this message because you are subscribed to the Google Groups > "jackson-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "jackson-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
