DefaultJsonMapper should have an additional constructor that takes a "strict"
boolean. If true, behavior is exactly as in 1.6 (the default constructor
should use true to preserve current behavior). If false, instead of throwing
an exception on JSON mapping failures, the exception should be swallowed and
the field set to null instead.
See discussion here: http://groups.google.com/group/restfb/msg/a720450b1b0c9021
Original issue reported on code.google.com by mark.a.a...@gmail.com on 30 Dec 2010 at 1:07
Original issue reported on code.google.com by
mark.a.a...@gmail.com
on 30 Dec 2010 at 1:07