Re: [jackson-user] Globally deserialize with underscore/hyphen/case insensitivity

There is no way to do this; you can have case-insensitive properties, or regular conversion (given POJO property, produce translated expected external value), but no arbitrary conversions applied on-the-fly. To support such mapping you would need to do 2-phase processing: first read content and

[jackson-user] Globally deserialize with underscore/hyphen/case insensitivity

For a property, anyCase, looking to be able to get a Jackson (2.8.x) ObjectMapper to recognize that any_case, any-case, ANYCASE, AnYcAsE are equivalent for purposes of deserialization without needing to use annotations on individual classes. I recognize that the following is possible:

Re: [jackson-user] JsonMappingException: Can not resolve PropertyFilter with id

I can't think of anything obvious. Since registration occurs via REST framework of some kind, it would seem like maybe registration is failing for some reason? Sometimes framework uses different `ObjectMapper` than user expects, leading to missing configuration. -+ Tatu +- On Thu, Jun 30, 2016

Re: [jackson-user] StackOverflowError in deeply nested JSON

Thank you! -+ Tatu +- On Fri, Jul 1, 2016 at 10:05 AM, Colin White wrote: > Thanks for the response. I'll take a closer look into the allocations on > the stack and report back. > > -Colin > > > On Thursday, 30 June 2016 22:33:41 UTC-7, Tatu Saloranta wrote: >> >> 50