已过时的列表 (Jackson JSON Processor)
您的浏览器已禁用 JavaScript。
已过时的接口&
接口和说明
已过时的类&
Since 1.9, use
Since 1.9, use
Since 1.9 use
Since 1.9 just don't use
Since 1.9 just don't use
Since 1.9 just don't use
Since 1.9, use
Since 1.9, use
Since 1.9 use
Starting with 1.7, functionality of this class has been
implemented both in base
(see methods
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 release
Since 1.9, use
M will be removed in Jackson 2.0
As of 1.9, use
Since 1.9, use
Since 1.9, use
Since 1.9 use
Since 1.9, use
Since 1.9 use
Since 1.9, use
Since 1.9.0: functionality demoted down to JsonParserBase
Since 1.9, use
Since 1.9 use
Since 1.9 sub-classes should just include code
from here as is.
Since 1.9 use
Since 1.9 use
As of 1.9, use
Since 1.9, use
Since 1.9 use
Since 1.9 use
Since 1.9 use
Since 1.9, use
Since 1.9 use
Since 1.9, use
Since 1.9, use
Since 1.9, use
Since 1.9, use
Since 1.9, use
Since 1.9, use
Since 1.9, sub-classes should just embed code from here
Since 1.9, use
Since 1.9 use
Since 1.9, use
已过时的注释类型&
注释类型和说明
instead (deprecated since version 1.5)
(since 1.6) Currently recommended annotation to use is
(with values ALWAYS or NON_NULL)
已过时的字段&
字段和说明
Since 1.9 just don't use
Since 1.9, use
Since 1.9 just don't use
Since 1.9 just don't use
accessor instead: will be removed from 2.0
As of 1.8, should use a per-ObjectMapper instance instead
of global singleton
已过时的方法&
方法和说明
since 1.7, should just override
of defining this method
since 1.7, should just override
of defining this method
since 1.7, should just override
of defining this method
since 1.7, should just override
of defining this method
this method is deprecated as it changes state, preventing immutability of instances
Since 1.9, if you must directly instantiate,
call method that takes handlers
As of 1.8; use the variant with more arguments
Since 1.7, call variant with more arguments
Since 1.7, call variant with more arguments
Since 1.9, use
since 1.9.0
since 1.9.0
since 1.9.0
Since 1.9, it is prefer
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 prefer
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 prefer
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 prefer
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, use
Since 1.9 use
Since 1.9 use
Since 1.9 use the non-deprecated version
Since 1.9 use
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)
since 1.9, use variant that takes JavaType
since 1.9, use variant that takes JavaType
Since 1.9, it is preferably to explicitly configure
this method also modifies existing instance which is
against immutable design goals of this class.
Since 1.9, it is preferably to explicitly configure
this method also modifies existing instance which is
against immutable design goals of this class.
Since 1.9, it is preferably to explicitly configure
this method also modifies existing instance which is
against immutable design goals of this class.
Since 1.9 just don't use
As of version 1.7, use version that exposes property object
instead of just its type (needed for contextual serializers)
As of version 1.8
Since 1.7, use
Since 1.9: use
Since 1.9 just don't use
Since 1.9, use
Since 1.9, use
Since 1.9, use
Since 1.9, use
Since 1.9, use
Since 1.9, use
Since 1.9, use
Since 1.9, use
Since 1.9, use
this method is deprecated as it changes state, preventing immutability of instances
since 1.9, use variant that takes second argument
Since 1.9, use
Since 1.9, use
Since 1.9, use
Since 1.9, it is preferable
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
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, use either
Module API instead
Since 1.8, use
As of version 1.8, it is preferable to call method in
or construct new instance with
since 1.9 should either use
to construct new instance, or configure through
Since 1.8, use
Since 1.9 - construct with deserializer
Since 1.9, instead, use
withContentTypeHandler and
withContentValueHandler methods.
Since 1.9 this method does nothing, so there is no
benefi it will be removed from 2.0.
Since 1.9, use
Since 1.9, use
Since 1.9, use
Since 1.9, use
since 1.7, use
Since 1.9, use
Since 1.7 use variant that takes
Use version that takes SerializerProvider instead.
Since 1.7 use variant that takes
Use version that takes SerializerProvider instead.
已过时的构造器&
构造器和说明
Since 1.9, should use factory methods instead
(since 1.9) Use the constructor that takes
Since 1.9, use variant that takes ValueInstantiator
Since 1.9, use variant that takes ValueInstantiator
Since 1.8, use variant that takes value serializer
Since 1.8; instead use variant that takes JavaType: this ensures
that type information is properly resolved
Since 1.8; should construct with resolved JavaType,
to ensure type has been properly resolved
Since 1.9, use variant that takes ValueInstantiator
Since 1.9, use variant that takes ValueInstantiator
Use variant that takes Key type and property information
As of 1.8, use version that takes valueSerializer
you can just set serializer factory with
Since 1.9 - use variant that takes deserializer
Since 1.9, use the constructor that takes 'defaultImpl'
已过时的枚举常量&
枚举常量和说明
As of 1.1, use接口 org.codehaus.jackson.map.JsonSerializableWithType的使用 (Jackson JSON Processor)
您的浏览器已禁用 JavaScript。
使用的程序包&
Package that contains concrete implementations of
well as the factory () for
constructing instances from various input data types
and programmatically (for structured types, arrays,
Utility classes for Mapper package.
Contains concrete
implementations
Jackson uses for the Tree model.
参数类型为的中的方法&
限定符和类型
方法和说明
SerializableWithTypeSerializer.(&value,
&provider)&
SerializableWithTypeSerializer.(&value,
&provider,
&typeSer)&
实现的中的类&
限定符和类型
Array types represent Java arrays, both primitive and object valued.
Type that represents things
but may or may not be instances of that interface.
Type that represents Java Collection types (Lists, Sets).
Type that represents Map- things that consist of key/value pairs but that
do not necessarily implement , but that do not have enough
introspection functionality to allow for some level of generic handling.
Type that represents "true" Java Map types.
Simple types are defined as anything other than one of recognized
container types (arrays, Collections, Maps).
实现的中的类&
限定符和类型
Container class that can be used to wrap any Object instances (including
nulls), and will serialize embedded in
General-purpose wrapper class that can be used to decorate serialized
value with arbitrary literal prefix and suffix.
实现的中的类&
限定符和类型
Node class that represents Arrays mapped from Json content.
Abstract base class common to all standard
implementations.
Numeric node that contains simple 64-bit integer values.
Value node that contains Base64 encoded binary value, which will be
output and stored as Json String value.
This concrete value class is used to contain boolean (true / false)
This intermediate base class is used for all container nodes,
specifically, array and object nodes.
Numeric node that contains values that do not fit in simple
integer (int, long) or floating point (double) values.
Numeric node that contains 64-bit ("double precision")
floating point values simple 32-bit integer values.
Numeric node that contains simple 32-bit integer values.
Numeric node that contains simple 64-bit integer values.
This singleton node class is generated to denote "missing nodes"
along paths that do not exist.
This singleton value class is used to contain explicit JSON null
Intermediate value node used for numeric nodes.
Node that maps to JSON Object structures in JSON content.
Value node that contains a wrapped POJO, to be serialized as
a JSON constructed through data mapping (usually done by
calling ).
Value node that contains a text value.
This intermediate base class is used for all leaf nodes, that is,
all non-container (array or object) nodes, except for the
"missing node".}