Jackson Release 2.9

Version 2.9 development is on-going, as of October 2016, with tentative goal of getting RC1 out during December 2016.

New Modules, status changes

Changes: compatibility

java.sql.Date

As per databind#219 java.sql.Date will finally use same "timestamp-or-String" determination as java.util.Date and java.util.Calendar. This means that with vanilla, unchanged settings, values will be serialized as numeric timestamps. Note that the default String serialization will still default to java.sql.Date.String(), and not to default formatting java.util.Date uses.

Major features of 2.9

Implemented

1. Add separate exception type for "pojo configuration problem" (InvalidDefinitionException), distinct from "json input" problem; in general to distinguish between bad configuration (server-side issue) and bad data (client issue) #1356
2. Per-property custom serialization inclusion (@JsonInclude(value=Include.CUSTOM, valueFilter=MyExcluder.class) #888
3. Per-property overwrite-vs-merge annotation/handling, to allow for merging of configuration information (for example) #1399
   • note: on-going work to increase coverage; some types (arrays, tree nodes) not yet supported

Under construction

Planned

1. Ability to override handling of null for deserialization #1402
2. Aliases, to allow migration: alternate property id names to accept (but not write) #1029
3. Allow pre-defining Object Ids; pluggable Object Id converters? #693
4. DeserializationFeature to automatically verify that value bound is full value and there is no trailing junk in input ("whole value verification")
5. "Safe" ObjectReader, ObjectWriter; that is, ones that does NOT throw checked exceptions (wrap IOExceptions), to work better with Java 8 Streams #779
6. Non-blocking JSON/Smile parser?
7. Rewrite of property/creator introspection code, to resolve most open issues wrt Creator auto-detection and name-detection
8. Support for @JsonIncludeProperties (opposite of @JsonIgnoreProperties) #1296
9. A way to force a supertype as type id to use during serialization: this is needed to avoid deserialization problems for things like concrete Hibernate collection type. #789

And possibly

• Protobuf: Schema building by hand
• Comma-separated "ints in a String" #1242

---

Change list

Changes, core

Annotations

• #103: Add JsonInclude.Include.CUSTOM, properties for specifying filter(s) to use
• #104: Add new properties in @JsonSetter: merge, null/contentNulls

Databind

• #219: SqlDateSerializer does not obey SerializationConfig.Feature.WRITE_DATES_AS_TIMESTAMPS
• #476: Allow "Serialize as POJO" using @JsonFormat(shape=Shape.OBJECT) class annotation
• #507: Support for default @JsonView for a class
• #888: Allow specifying custom exclusion comparator via @JsonInclude, using JsonInclude.Include.CUSTOM
• #1035: @JsonAnySetter assumes key of String, does not consider declared type
• #1284: Make StdKeySerializers use new JsonGenerator.writeFieldId() for int/long keys
• #1320: Add ObjectNode.put(String, BigInteger)
• #1341: DeserializationFeature.FAIL_ON_MISSING_EXTERNAL_TYPE_ID_PROPERTY
• #1356: Differentiate between input and code exceptions on deserialization
• #1369: Improve @JsonCreator detection via AnnotationIntrospector by passing MappingConfig
• #1371: Add MapperFeature.INFER_CREATOR_FROM_CONSTRUCTOR_PROPERTIES to allow disabling use of @CreatorProperties as explicit @JsonCreator equivalent
• #1376: Add ability to disable JsonAnySetter/JsonAnyGetter via mixin
• #1399: Add support for @JsonSetter(merge=OptBoolean.TRUE) to allow "deep update"
• #1406: ObjectMapper.readTree() methods do not return null on end-of-input
• #1428: Allow @JsonValue on a field, not just getter

Changes, data formats

YAML

• #76: Add YAMLGenerator.Feature.LITERAL_BLOCK_STYLE for String output

Changes, other modules

JSON Schema

• #119: dependencies property should not be an Array but Object