Closed GoogleCodeExporter closed 9 years ago
Glad to know that you could register a custom type adapter to address your
use-case.
We wouldn't like to change the design of Gson to silently ignore invalid Enum
values
as it may mask real bugs. Some organization prefer the fail-fast approach to
detect
bugs.
Original comment by inder123
on 15 Oct 2009 at 4:10
Sorry for jumping in a bit late here. What version of Gson are you running
that requires you to register both a custom deserializer and an instance
creator. I know we had that bug a while back, but I thought it was fixed in
version 1.3 and later.
Is it possible to use the Gson versioning to protect you from the
sender/receiver incompatibilities? The common approach for API versioning is
that the client will request the API version it would like to use with the
server. The server is then able to process and respond to the client without
breaking backward compatibility. As new features get added to API calls (or new
API calls emerge) then the server should support a new version.
Original comment by joel.leitch@gmail.com
on 21 Aug 2010 at 8:31
Original comment by inder123
on 3 Nov 2010 at 1:45
I do not consider this a Gson issue, but rather a versioning issue between the
client and server.
Original comment by joel.leitch@gmail.com
on 22 Mar 2011 at 10:15
Original issue reported on code.google.com by
danw...@gmail.com
on 12 Oct 2009 at 8:29