Provide ability to register different FieldNamingStrategies for serialization and deserialization

[GoogleCodeExporter]

See discussion at: 
https://groups.google.com/forum/?hl=en#!topic/google-gson/ZYnHXcY6IBg

Original issue reported on code.google.com by inder123 on 8 May 2011 at 8:25

[GoogleCodeExporter]

Is this possible enhancement just to be able to register different 
FieldNamingStrategies for serialization and deserialization, or is it also to 
address adding the ability to specify name translation preferences in both 
directions: from Java field to JSON element, and from JSON element to Java 
field?

To clarify, might this enhancement include the ability to deserialize a JSON 
element without consideration for the case of the characters in the JSON 
element name -- that is, to possibly allow a case-insensitive binding between 
Java field and JSON element names, along the lines of what's described at 
http://stackoverflow.com/questions/6332651?

Original comment by Programm...@gmail.com on 14 Jun 2011 at 12:24

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

This is rarely what you want. Even case insensitivity is strange because 
JavaScript is case sensitive. Plus, there are weird situations with 
capitalization rules for non-ASCII characters.

Original comment by limpbizkit on 18 Mar 2012 at 8:21

• Changed state: WontFix
• Added labels: ****
• Removed labels: ****