public final Enum MapperFeature

Feature that determines if Enum deserialization should be case sensitive or not. If enabled, Enum deserialization will ignore case, that is, case of incoming String value and enum id (depending on other settings, either `name()`, `toString()`, or explicit override) do not need to match.

This should allow both Enum-as-value deserialization and Enum-as-Map-key, but latter only works since Jackson 2.12 (due to incomplete implementation).

Feature is disabled by default.

Since

2.9

Feature that will allow for more forgiving deserialization of incoming JSON. If enabled, the bean properties will be matched using their lower-case equivalents, meaning that any case-combination (incoming and matching names are canonicalized by lower-casing) should work.

Note that there is additional performance overhead since incoming property names need to be lower-cased before comparison, for cases where there are upper-case letters. Overhead for names that are already lower-case should be negligible.

Feature is disabled by default.

Since

2.5

Feature that permits parsing some enumerated text-based value types but ignoring the case of the values on deserialization: for example, date/time type deserializers. Support for this feature depends on deserializer implementations using it.

Note, however, that regular Enum types follow ACCEPT_CASE_INSENSITIVE_ENUMS setting instead.

Feature is disabled by default.

Since

2.10

Feature that determines whether coercions from secondary representations are allowed for simple non-textual scalar types: numbers and booleans. This includes `primitive` types and their wrappers, but excludes `java.lang.String` and date/time types.

When feature is disabled, only strictly compatible input may be bound: numbers for numbers, boolean values for booleans. When feature is enabled, conversions from JSON String are allowed, as long as textual value matches (for example, String "true" is allowed as equivalent of JSON boolean token `true`; or String "1.0" for `double`).

Note that it is possible that other configurability options can override this in closer scope (like on per-type or per-property basis); this is just the global default.

Feature is enabled by default (for backwards compatibility since this was the default behavior)

Since

2.9

Feature that when enabled will allow explicitly named properties (i.e., fields or methods annotated with com.fasterxml.jackson.annotation.JsonProperty("explicitName")) to be re-named by a PropertyNamingStrategy, if one is configured.

Feature is disabled by default.

Since

2.7

Feature that determines whether member fields declared as 'final' may be auto-detected to be used mutators (used to change value of the logical property) or not. If enabled, 'final' access modifier has no effect, and such fields may be detected according to usual visibility and inference rules; if disabled, such fields are NOT used as mutators except if explicitly annotated for such use.

Feature is enabled by default, for backwards compatibility reasons.

Since

2.2

Feature that when enabled will allow getters with is-Prefix also for non-boolean return types; if disabled only methods that return boolean or Boolean qualify as "is getters".

Feature is disabled by default for backwards compatibility.

Since

2.14

Feature that determines whether nominal property type of Void is allowed for Getter methods to indicate null valued pseudo-property or not. If enabled, such properties are recognized (see [databind#2675] for reasons -- mostly things related to frameworks, code generation); if disabled, such property accessors (or at least getters) are ignored.

Feature is disabled by default (in 2.12) for backwards compatibility.

Since

2.12

Feature that determines whether ObjectReader applies default values defined in class definitions in cases where the input data omits the relevant values.

Not all modules will respect this feature. Initially, only jackson-module-scala will respect this feature but other modules will add support over time.

Feature is enabled by default.

Since

2.13

Feature that determines whether "creator" methods are automatically detected by consider public constructors, and static single argument methods with name "valueOf". If disabled, only methods explicitly annotated are considered creator methods (except for the no-arg default constructor which is always considered a factory method).

Note that this feature has lower precedence than per-class annotations, and is only used if there isn't more granular configuration available.

Feature is enabled by default.

Feature that determines whether non-static fields are recognized as properties. If yes, then all public member fields are considered as properties. If disabled, only fields explicitly annotated are considered property fields.

Note that this feature has lower precedence than per-class annotations, and is only used if there isn't more granular configuration available.

Feature is enabled by default.

Feature that determines whether regular "getter" methods are automatically detected based on standard Bean naming convention or not. If yes, then all public zero-argument methods that start with prefix "get" are considered as getters. If disabled, only methods explicitly annotated are considered getters.

Note that since version 1.3, this does NOT include "is getters" (see AUTO_DETECT_IS_GETTERS for details)

Note that this feature has lower precedence than per-class annotations, and is only used if there isn't more granular configuration available.

Feature is enabled by default.

Feature that determines whether "is getter" methods are automatically detected based on standard Bean naming convention or not. If yes, then all public zero-argument methods that start with prefix "is", and whose return type is boolean are considered as "is getters". If disabled, only methods explicitly annotated are considered getters.

Note that this feature has lower precedence than per-class annotations, and is only used if there isn't more granular configuration available.

Feature is enabled by default.

Feature that determines whether "setter" methods are automatically detected based on standard Bean naming convention or not. If yes, then all public one-argument methods that start with prefix "set" are considered setters. If disabled, only methods explicitly annotated are considered setters.

Note that this feature has lower precedence than per-class annotations, and is only used if there isn't more granular configuration available.

Feature is enabled by default.

Setting that may be enabled to reconfigure default com.fasterxml.jackson.databind.jsontype.PolymorphicTypeValidator used by legacy ObjectMapper.enableDefaultTyping() methods as well as default used for annotation-based polymorphic handling so that it uses com.fasterxml.jackson.databind.jsontype.DefaultBaseTypeLimitingValidator. This will block use of a set of "unsafe" base types such as java.lang.Object through methods that do not require passing of explicit com.fasterxml.jackson.databind.jsontype.PolymorphicTypeValidator. It is still possible to override one used; this only affects default settings.

Enabling of this setting is strongly recommended.

Feature is disabled by default in 2.x for backwards compatibility reasons: it will become default setting (and feature likely removed) in 3.0.

Since

2.11

Feature that determines whether method and field access modifier settings can be overridden when accessing properties. If enabled, method java.lang.reflect.AccessibleObject#setAccessible may be called to enable access to otherwise unaccessible objects.

Note that this setting may have significant performance implications, since access override helps remove costly access checks on each and every Reflection access. If you are considering disabling this feature, be sure to verify performance consequences if usage is performance sensitive. Also note that performance effects vary between Java platforms (JavaSE vs Android, for example), as well as JDK versions: older versions seemed to have more significant performance difference.

Conversely, on some platforms, it may be necessary to disable this feature as platform does not allow such calls. For example, when developing Applets (or other Java code that runs on tightly restricted sandbox), it may be necessary to disable the feature regardless of performance effects.

Feature is enabled by default.

Feature that determines whether properties that have no view annotations are included in JSON serialization views (see com.fasterxml.jackson.annotation.JsonView for more details on JSON Views). If enabled, non-annotated properties will be included; when disabled, they will be excluded. So this feature changes between "opt-in" (feature disabled) and "opt-out" (feature enabled) modes.

Default value is enabled, meaning that non-annotated properties are included in all views if there is no com.fasterxml.jackson.annotation.JsonView annotation.

Feature is enabled by default.

Feature that determines whether multiple registrations of same module should be ignored or not; if enabled, only the first registration call results in module being called, and possible duplicate calls are silently ignored; if disabled, no checking is done and all registration calls are dispatched to module.

Definition of "same module" is based on using Module#getTypeId(); modules with same non-null type id are considered same for purposes of duplicate registration. This also avoids having to keep track of actual module instances; only ids will be kept track of (and only if this feature is enabled).

Feature is enabled by default.

Since

2.5

Setting that determines what happens if an attempt is made to explicitly "merge" value of a property, where value does not support merging; either merging is skipped and new value is created (true) or an exception is thrown (false).

Feature is enabled by default, to allow use of merge defaults even in presence of some unmergeable properties.

Since

2.9

Feature that enables inferring builder type bindings from the value type being deserialized. This requires that the generic type declaration on the value type match that on the builder exactly: mismatched type declarations are not necessarily detected by databind.

Feature is enabled by default which means that deserialization does support deserializing types via builders with type parameters (generic types).

See: databind#921

Since

2.12

Feature that determines handling of java.beans.ConstructorProperties annotation: when enabled, it is considered as alias of com.fasterxml.jackson.annotation.JsonCreator, to mean that constructor should be considered a property-based Creator; when disabled, only constructor parameter name information is used, but constructor is NOT considered an explicit Creator (although may be discovered as one using other annotations or heuristics).

Feature is mostly used to help inter-operability with frameworks like Lombok that may automatically generate ConstructorProperties annotation but without necessarily meaning that constructor should be used as Creator for deserialization.

Feature is enabled by default.

Since

2.9

Feature that determines whether member mutators (fields and setters) may be "pulled in" even if they are not visible, as long as there is a visible accessor (getter or field) with same name. For example: field "value" may be inferred as mutator, if there is visible or explicitly marked getter "getValue()". If enabled, inferring is enabled; otherwise (disabled) only visible and explicitly annotated accessors are ever used.

Note that 'getters' are never inferred and need to be either visible (including bean-style naming) or explicitly annotated.

Feature is enabled by default.

Since

2.2

Feature that determines that forces call to java.lang.reflect.AccessibleObject#setAccessible even for public accessors -- that is, even if no such call is needed from functionality perspective -- if call is allowed (that is, CAN_OVERRIDE_ACCESS_MODIFIERS is set to true). The main reason to enable this feature is possible performance improvement as JDK does not have to perform access checks; these checks are otherwise made for all accessors, including public ones, and may result in slower Reflection calls. Exact impact (if any) depends on Java platform (Java SE, Android) as well as JDK version.

Feature is enabled by default, for legacy reasons (it was the behavior until 2.6)

Since

2.7

Feature that determines how transient modifier for fields is handled: if disabled, it is only taken to mean exclusion of the field as an accessor; if true, it is taken to imply removal of the whole property.

Feature is disabled by default, meaning that existence of `transient` for a field does not necessarily lead to ignoral of getters or setters but just ignoring the use of field for access.

Since

2.6

Feature that determines whether getters (getter methods) can be auto-detected if there is no matching mutator (setter, constructor parameter or field) or not: if set to true, only getters that match a mutator are auto-discovered; if false, all auto-detectable getters can be discovered.

Feature is disabled by default.

Feature that determines what happens when deserializing to a registered sub-type (polymorphic deserialization), but no type information has been provided. If enabled, then an InvalidTypeIdException will be thrown; if disabled then the deserialization may proceed without the type information if sub-type is legit target (non-abstract).

Feature is enabled by default for backwards-compatibility (same behavior as in Jackson 2.14 and earlier).

Since

2.15

Feature that defines whether Creator properties (ones passed through constructor or static factory method) should be sorted in their declaration order if SORT_CREATOR_PROPERTIES_FIRST is also enabled. This is usually used to prevent alphabetic sorting for Creator properties even if SORT_PROPERTIES_ALPHABETICALLY is enabled for other types of properties.

Feature is disabled by default (for backwards compatibility) in 2.x

Since

2.18

Feature that defines whether Creator properties (ones passed through constructor or static factory method) should be sorted before other properties for which no explicit order is specified, in case where alphabetic ordering is to be used for such properties. Note that in either case explicit order (whether by name or by index) will have precedence over this setting.

Feature is enabled by default.

Since

2.12

Feature that defines default property serialization order used for POJO properties. If enabled, default ordering is alphabetic (similar to how com.fasterxml.jackson.annotation.JsonPropertyOrder#alphabetic() works); if disabled, order is unspecified (based on what JDK gives us, which may be declaration order, but is not guaranteed).

Note that this is just the default behavior and can be overridden by explicit overrides in classes (for example with com.fasterxml.jackson.annotation.JsonPropertyOrder annotation)

Feature is disabled by default.

Feature that determines whether annotation introspection is used for configuration; if enabled, configured AnnotationIntrospector will be used: if disabled, no annotations are considered.

Feature is enabled by default.

Feature that specifies whether the declared base type of a polymorphic value is to be used as the "default" implementation, if no explicit default class is specified via @JsonTypeInfo.defaultImpl annotation.

Note that feature only has effect on deserialization of regular polymorphic properties: it does NOT affect non-polymorphic cases, and is unlikely to work with Default Typing.

Feature is disabled by default for backwards compatibility.

Since

2.10

Feature that determines whether otherwise regular "getter" methods (but only ones that handle Collections and Maps, not getters of other type) can be used for purpose of getting a reference to a Collection and Map to modify the property, without requiring a setter method. This is similar to how JAXB framework sets Collections and Maps: no setter is involved, just getter.

Note that such getters-as-setters methods have lower precedence than setters, so they are only used if no setter is found for the Map/Collection property.

Feature is enabled by default.

Feature that determines whether the type detection for serialization should be using actual dynamic runtime type, or declared static type. Note that deserialization always uses declared static types since no runtime types are available (as we are creating instances after using type information).

This global default value can be overridden at class, method or field level by using JsonSerialize#typing annotation property.

Feature is disabled by default which means that dynamic runtime types are used (instead of declared static types) for serialization.

Feature that may be enabled to enforce strict compatibility with Bean name introspection, instead of slightly different mechanism Jackson defaults to. Specific difference is that Jackson always lower cases leading upper-case letters, so "getURL()" becomes "url" property; whereas standard Bean naming only lower-cases the first letter if it is NOT followed by another upper-case letter (so "getURL()" would result in "URL" property).

Feature is disabled by default for backwards compatibility purposes: earlier Jackson versions used Jackson's own mechanism.

Since

2.5

Feature that can be enabled to make property names be overridden by wrapper name (usually detected with annotations as defined by AnnotationIntrospector#findWrapperName. If enabled, all properties that have associated non-empty Wrapper name will use that wrapper name instead of property name. If disabled, wrapper name is only used for wrapping (if anything).

Feature is disabled by default.

Since

2.1