Re: [jackson-user] Serialization of any object with parent-child relationships without outputing the ID value

On Thu, Feb 16, 2017 at 1:43 PM, David Hayek wrote: > If I have to serialize an object that I can not annotate and that contains > parent-child relationship, such as a DefaultMutableTreeNode, I can avoid the > infinite recursion/stack overflow problem by supplying an ObjectIdGenerator > from the f

[jackson-user] Re: Android - Problem deserialising JSON to object in 'release' builds

Turns out the problem was due to the class I was using to deserialise my JSON was declared within my activity class, therefore an inner class. I read that inner classes can be used with the Jackson ObjectMapper as long as they were declared static which this was, so not exactly sure why it did

[jackson-user] Serialization of any object with parent-child relationships without outputing the ID value

If I have to serialize an object that I can not annotate and that contains parent-child relationship, such as a *DefaultMutableTreeNode*, I can avoid the infinite recursion/stack overflow problem by supplying an *ObjectIdGenerator *from the *findObjectIdInfo*() method in a subclass of the *Jac