Deprecated API
Contents
-
Deprecated Interfaces
-
Deprecated ClassesClassDescriptionMoved to
DefaultPrettyPrinter
; will be removed in Jackson 2.0Since 1.9.0: functionality demoted down to JsonParserBaseSince 1.9 sub-classes should just include code from here as is.Since 1.9, sub-classes should just embed code from hereSince 1.9, useObjectArrayDeserializer
instead.Since 1.9, usePrimitiveArrayDeserializers
instead.Since 1.9, useContainerDeserializerBase
instead.Since 1.9, useContainerDeserializerBase
instead.Starting with 1.7, functionality of this class has been implemented both in baseSerializerFactory
(see methods likeSerializerFactory.withAdditionalSerializers(Serializers)
) and through new Module API. As such, this class is not the best way to add custom functionality, and will likely be removed from 2.0 releaseSince 1.9, useJsonNodeDeserializer
instead.Since 1.9, useEnumDeserializer
instead.Since 1.9, useEnumResolver
instead.Since 1.9, useFromStringDeserializer
instead.Since 1.9, useJsonNodeDeserializer
instead.Since 1.9, useMapDeserializer
instead.Since 1.9, useStdDeserializer
instead.Since 1.9 useCalendarDeserializer
instead.Since 1.9 useClassDeserializer
instead.Since 1.9 useStringDeserializer
instead.Since 1.9, useStdKeyDeserializer
instead.Since 1.9, useStdScalarDeserializer
instead.Since 1.9, useThrowableDeserializer
instead.Since 1.9, useUntypedObjectDeserializer
instead.As of 1.9, useDeserializers.Base
insteadSince 1.9 just don't useSince 1.9 just don't useSince 1.9 just don't useSince 1.9 useStdArraySerializers
Since 1.9 useStdContainerSerializers
insteadSince 1.9 useEnumSerializer
Since 1.9 useStdJdkSerializers
Since 1.9 useMapSerializer
Since 1.9 useSerializerBase
instead.Since 1.9 useSerializerBase
Since 1.9 useStdKeySerializer
insteadSince 1.9, useDateSerializer
insteadSince 1.9, useDateSerializer
insteadSince 1.9, useDateSerializer
insteadSince 1.9, useStringSerializer
insteadSince 1.9, useDateSerializer
insteadSince 1.9 useToStringSerializer
As of 1.9, useSerializers.Base
instead
-
Deprecated Annotation TypesAnnotation TypeDescriptionUse
JsonProperty
instead (deprecated since version 1.5)(since 1.6) Currently recommended annotation to use isJsonSerialize.include()
(with valuesALWAYS
orNON_NULL
)
-
Deprecated FieldsFieldDescriptionUse
JsonNodeDeserializer.getDeserializer(java.lang.Class<?>)
accessor instead: will be removed from 2.0Since 1.9 just don't useSince 1.9 just don't useSince 1.9 just don't useSince 1.9, useStdKeySerializers
insteadAs of 1.8, should use a per-ObjectMapper instance instead of global singleton
-
Deprecated MethodsMethodDescriptionsince 1.7, should just override
JsonGeneratorBase.writeEndArray()
instead of defining this methodsince 1.7, should just overrideJsonGeneratorBase.writeEndObject()
instead of defining this methodsince 1.7, should just overrideJsonGeneratorBase.writeStartArray()
instead of defining this methodsince 1.7, should just overrideJsonGeneratorBase.writeStartObject()
instead of defining this methodUseJsonFactory.disable(JsonGenerator.Feature)
insteadUseJsonFactory.disable(JsonParser.Feature)
insteadUseJsonFactory.enable(JsonGenerator.Feature)
insteadUseJsonFactory.enable(JsonParser.Feature)
insteadUseJsonFactory.isEnabled(JsonGenerator.Feature)
insteadUseJsonFactory.isEnabled(JsonParser.Feature)
insteadUseJsonNode.path(int)
insteadUseJsonNode.path(String)
insteadSince 1.9, useJsonNode.asBoolean()
insteadSince 1.9, useJsonNode.asBoolean()
insteadSince 1.9, useJsonNode.asDouble()
insteadSince 1.9, useJsonNode.asDouble()
insteadSince 1.9, useJsonNode.asInt()
insteadSince 1.9, useJsonNode.asInt()
insteadSince 1.9, useJsonNode.asLong()
insteadSince 1.9, useJsonNode.asLong()
insteadSince 1.9, useJsonNode.asText()
insteadUseJsonParser.disable(Feature)
insteadUseJsonParser.enable(Feature)
insteadUseJsonParser.isEnabled(Feature)
insteadSince 1.9 useBeanDescription.findProperties()
Since 1.9 useBeanDescription.findProperties()
Since 1.9 use the non-deprecated versionSince 1.9 useBeanDescription.findProperties()
since 1.9, use variant that takes JavaTypesince 1.9, use variant that takes JavaTypeSince 1.7 use variant that takesDeserializationContext
Since 1.7 use variant that takesDeserializationContext
since 1.9.0since 1.9.0since 1.9.0Since 1.9 - construct with deserializerSince 1.7, useSettableBeanProperty.getName()
instead.Since 1.9: useSettableBeanProperty.getPropertyIndex()
insteadSince 1.9, it is preferable to useDeserializationConfig.without(org.codehaus.jackson.map.DeserializationConfig.Feature...)
instead; this method is deprecated as it modifies current instance instead of creating a new one (as the goal is to make this class immutable)Since 1.9, it is preferable to useDeserializationConfig.with(org.codehaus.jackson.map.DeserializationConfig.Feature...)
instead; this method is deprecated as it modifies current instance instead of creating a new one (as the goal is to make this class immutable)Since 1.9, it is preferably to explicitly configure instances; this method also modifies existing instance which is against immutable design goals of this class.Since 1.9, it is preferable to useDeserializationConfig.without(org.codehaus.jackson.map.DeserializationConfig.Feature...)
andDeserializationConfig.with(org.codehaus.jackson.map.DeserializationConfig.Feature...)
instead; this method is deprecated as it modifies current instance instead of creating a new one (as the goal is to make this class immutable)Since 1.9 just don't useSince 1.9 just don't useSince 1.9 useMapperConfig.withAppendedAnnotationIntrospector(AnnotationIntrospector)
instead; this method is deprecated as it changes state, preventing immutability of instancesSince 1.9, it is preferably to explicitly configure instances; this method also modifies existing instance which is against immutable design goals of this class.Since 1.9 useMapperConfig.withInsertedAnnotationIntrospector(AnnotationIntrospector)
instead; this method is deprecated as it changes state, preventing immutability of instancesSince 1.8, use eitherMapperConfig.withAnnotationIntrospector(AnnotationIntrospector)
or Module API insteadAs of version 1.8, it is preferable to call method inObjectMapper
instead; or construct new instance withMapperConfig.withDateFormat(DateFormat)
Since 1.9, useObjectMapper.writerWithDefaultPrettyPrinter()
instead.Since 1.9, useObjectMapper.writer(FilterProvider)
instead.Since 1.9, useObjectMapper.writer(FilterProvider)
instead.Since 1.9, useObjectMapper.reader(FormatSchema)
instead.Since 1.9, useObjectMapper.writer(FilterProvider)
instead.Since 1.9, useObjectMapper.writerWithType(Class)
instead.Since 1.9, useObjectMapper.writerWithType(JavaType)
instead.Since 1.9, useObjectMapper.writerWithType(TypeReference)
instead.Since 1.9, useObjectMapper.readerForUpdating(java.lang.Object)
instead.Since 1.9, useObjectMapper.writerWithView(Class)
instead.Since 1.9 this method does nothing, so there is no benefit from overriding it; it will be removed from 2.0.As of 1.8; use the variant with more argumentsUse version that takesSerializerProvider
instead.Use version that takesSerializerProvider
instead.Since 1.9, it is preferable to useSerializationConfig.without(org.codehaus.jackson.map.SerializationConfig.Feature...)
instead; this method is deprecated as it modifies current instance instead of creating a new one (as the goal is to make this class immutable)Since 1.9, it is preferable to useSerializationConfig.with(org.codehaus.jackson.map.SerializationConfig.Feature...)
instead; this method is deprecated as it modifies current instance instead of creating a new one (as the goal is to make this class immutable)Since 1.9, it is preferably to explicitly configure instances; this method also modifies existing instance which is against immutable design goals of this class.Since 1.9, it is preferable to useSerializationConfig.without(org.codehaus.jackson.map.SerializationConfig.Feature...)
andSerializationConfig.with(org.codehaus.jackson.map.SerializationConfig.Feature...)
instead; this method is deprecated as it modifies current instance instead of creating a new one (as the goal is to make this class immutable)Since 1.8, useSerializationConfig.withDateFormat(java.text.DateFormat)
instead.since 1.9 should either useSerializationConfig.withSerializationInclusion(org.codehaus.jackson.map.annotate.JsonSerialize.Inclusion)
to construct new instance, or configure throughObjectMapper
Since 1.8, useSerializationConfig.withView(java.lang.Class<?>)
insteadSince 1.7, call variant with more argumentsSince 1.7, call variant with more argumentsAs of version 1.7, use version that exposes property object instead of just its type (needed for contextual serializers)As of version 1.7, use version that exposes property object instead of just its type (needed for contextual serializers)As of version 1.7, use version that exposes property object instead of just its type (needed for contextual serializers)As of version 1.7, use version that exposes property object instead of just its type (needed for contextual serializers)As of version 1.7, use version that exposes property object instead of just its type (needed for contextual serializers)As of version 1.8Since 1.9, if you must directly instantiate, call method that takes handlersUseTypeFactory.type(Type)
insteadUseTypeFactory.type(Type)
insteadUseTypeFactory.type(Type)
insteadsince 1.9, use variant that takes second argumentsince 1.7, useEnumValues.serializedValueFor(java.lang.Enum<?>)
insteadSince 1.9, should not be used; instead, usewithContentTypeHandler
andwithContentValueHandler
methods.
-
Deprecated ConstructorsConstructorDescription(since 1.9) Use the constructor that takes
ValueInstantiator
insteadSince 1.9, use variant that takes ValueInstantiatorSince 1.9, use variant that takes ValueInstantiatorSince 1.9 - use variant that takes deserializerSince 1.9, use variant that takes ValueInstantiatorSince 1.9, use variant that takes ValueInstantiatorSince 1.9, should use factory methods insteadSince 1.9, use the constructor that takes 'defaultImpl'Use other constructors instead; note that you can just set serializer factory withObjectMapper.setSerializerFactory(org.codehaus.jackson.map.SerializerFactory)
Use variant that takes Key type and property informationAs of 1.8, use version that takes valueSerializersince 1.8Since 1.8, use variant that takes value serializersince 1.8Since 1.8; instead use variant that takes JavaType: this ensures that type information is properly resolvedSince 1.8; should construct with resolvedJavaType
, to ensure type has been properly resolved
-
Deprecated Enum ConstantsEnum ConstantDescription