WRT to the following question:
I wish to know
- Is Jackson specifying that the json date format should be normalised to a unix time integer?
Follow-up questions ...
- Has there been a change in its stance anytime recently?
- Shouldn't a date format be normalised to the same format provided by jaxb xml output?
- why/why not?
- any effort put into resolving this issue?
- has RestEasy provided a json provider mitigation that would output json date in a generally recognisable date format?
This is also controlled by a feature on the ObjectMapper (at least in 1.9.11, and possibly earlier):
I don't see how to declaratively do the equivalent on the object definition itself.
Sorry people for yelling out loud - I found the answers here
http://wiki.fasterxml.com/JacksonFAQDateHandling,
here
http://wiki.fasterxml.com/JacksonFAQ#Serializing_Dates,
here
http://wiki.fasterxml.com/JacksonHowToCustomSerializers
here
http://jackson.codehaus.org/1.1.2/javadoc/org/codehaus/jackson/map/util/StdDateFormat.html
Using the @JsonSerialize(using= ... ) way: