On Fri, Apr 21, 2017 at 3:06 PM, Andrew Joseph wrote:
> Actually looks like DeserializationProblemHandler handles most of what I
> want after all! I'm really only focused on collecting and recovering from
> errors made by the user submitting the json -not my own incompetence as a
> developer.
> ha
If javaslang List implementation is a mutable `List`, you can simply
register abstract type mapping:
SimpleModule m = new SimpleModule(...);
m.addAbstractTypeMapping(List.class, SlangList.class);
mapper.registerModule(m);
-+ Tatu +-
On Thu, Apr 20, 2017 at 5:21 PM, Santhosh Kumar wrote
Actually looks like DeserializationProblemHandler handles most of what I
want after all! I'm really only focused on collecting and recovering from
errors made by the user submitting the json -not my own incompetence as a
developer.
handleWeirdStringValue and handleWeirdNumberValue seem to recov
Thanks for confirming.
On Monday, April 17, 2017 at 5:41:32 AM UTC+5:30, Tatu Saloranta wrote:
>
> Yes, they are immutable and thread-safe.
>
> -+ Tatu +-
>
> On Sat, Apr 15, 2017 at 7:45 AM, Anurag Laddha > wrote:
> > Can i use the same com.fasterxml.jackson.core.type.TypeReference
> instanc
Hi Tatu,
Thanks for your response.
On the first issue, with polymorphic json serde, I'm still grappling with
the how-to for including the class info handling without the annotations.
The second issue is, the reasoning behind having custom serde on the
superclass (Document) to begin with. I ha