Support for custom property names for mapping and json

[chrislovecnm]

Hi

I am excited to see you added json serialization, because I am guessing that it is going to be faster much faster than components that use reflection or annotations. One component that is missing is the capability to set custom json field names.

Jackson allows the setting of field names via annotations such as:

@JsonProperty("name")

Is it possible to have the same type of support for both json and map instantiation of properties?

[jodastephen]

To date, Joda-Beans serialization has been seen as a mechanism for transporting beans across the network without customization - the bean is the schema and defines the field names. Basic support has been added for reading old data, handling class, enum and field renames.

I'm not completely averse to adding a @PropertySerialization annotation that allows customization of the output, but it does make the system more complex. The real question is why does the serialized name need to be different?

[chrislovecnm]

The issue main issue with json are with like data-value

Because of that I cannot serialize from json to joda bean

[jodastephen]

I suppose that this requirement could be handled with a field name strategy, ie. convert lowerCamelCase to dash-separated (lower-camel-case).

Just so you are aware, my biggest problem with this is not the specific requirement (which is manageable), but the potential for other requirements to grow that turn Joda-Beans into a Jackson-like beast which allows any format of XML/JSON to be generated (ie a mapping tool). The serialization aspect of Joda-Beans was originally designed for serialization, where the format of the data is less important.

I do expect to make further enhancements to the serialization part, so I'll see what I can do at that point.

[chrislovecnm]

Been open too long ... closing