1. Overview

In this article, we’ll do a deep dive into Jackson Annotations.

We’ll see how to use the existing annotations, how to create custom ones and finally – how to disable them.

However, there is no theName field in our target entity – there is only a name field. Now – we don’t want to change the entity itself – we just need a little more control over the unmarshalling process – by annotating the constructor with @JsonCreator and using the @JsonProperty annotation as well:

public class BeanWithCreator {

public int id;

public String name;

@JsonCreator

public BeanWithCreator(

@JsonProperty("id") int id,

@JsonProperty("theName") String name) {

this.id = id;

this.name = name;

}

Let’s see this in action:

@Test

public void whenDeserializingUsingJsonCreator_thenCorrect()

throws IOException {

String json = "{\"id\":1,\"theName\":\"My bean\"}";

BeanWithCreator bean = new ObjectMapper()

.readerFor(BeanWithCreator.class)

.readValue(json);

assertEquals("My bean", bean.name);

}

3.2. @JacksonInject

@JacksonInject is used to indicate a property that will get its value from the injection and not from the JSON data.

In the following example – we use @JacksonInject to inject the property id:

public class BeanWithInject {

@JacksonInject

public int id;

public String name;

}

And here’s how this works:

@Test

public void whenDeserializingUsingJsonInject_thenCorrect()

throws IOException {

String json = "{\"name\":\"My bean\"}";

InjectableValues inject = new InjectableValues.Std()

.addValue(int.class, 1);

BeanWithInject bean = new ObjectMapper().reader(inject)

.forType(BeanWithInject.class)

.readValue(json);

assertEquals("My bean", bean.name);

assertEquals(1, bean.id);

}

3.3. @JsonAnySetter

@JsonAnySetter allows you the flexibility of using a Map as standard properties. On de-serialization, the properties from JSON will simply be added to the map.

Let’s see how this works – we’ll use @JsonAnySetter to deserialize the entity ExtendableBean:

public class ExtendableBean {

public String name;

private Map<String, String> properties;

@JsonAnySetter

public void add(String key, String value) {

properties.put(key, value);

}

This is the JSON we need to deserialize:

{

"name":"My bean",

"attr2":"val2",

"attr1":"val1"

}

And here’s how this all ties in together:

@Test

public void whenDeserializingUsingJsonAnySetter_thenCorrect()

throws IOException {

String json

= "{\"name\":\"My bean\",\"attr2\":\"val2\",\"attr1\":\"val1\"}";

ExtendableBean bean = new ObjectMapper()

.readerFor(ExtendableBean.class)

.readValue(json);

assertEquals("My bean", bean.name);

assertEquals("val2", bean.getProperties().get("attr2"));

}

3.4. @JsonSetter

@JsonSetter is an alternative to @JsonProperty – used to mark the method as a setter method.

This is super useful when we need to read some JSON data but the target entity class doesn’t exactly match that data, and so we need to tune the process to make it fit.

In the following example, we’ll specify the method setTheName() as the setter of the name property in our MyBeanentity:

public class MyBean {

public int id;

private String name;

@JsonSetter("name")

public void setTheName(String name) {

this.name = name;

}

Now, when we need to unmarshall some JSON data – this works perfectly well:

@Test

public void whenDeserializingUsingJsonSetter_thenCorrect()

throws IOException {

String json = "{\"id\":1,\"name\":\"My bean\"}";

MyBean bean = new ObjectMapper()

.readerFor(MyBean.class)

.readValue(json);

assertEquals("My bean", bean.getTheName());

}

3.5. @JsonDeserialize

@JsonDeserialize is used to indicate the use of a custom deserializer.

Let’s see how that plays out – we’ll use @JsonDeserialize to deserialize the eventDate property with the CustomDateDeserializer:

public class Event {

public String name;

@JsonDeserialize(using = CustomDateDeserializer.class)

public Date eventDate;

}

Here’s the custom deserializer:

public class CustomDateDeserializer

extends StdDeserializer<Date> {

private static SimpleDateFormat formatter

= new SimpleDateFormat("dd-MM-yyyy hh:mm:ss");

public CustomDateDeserializer() {

this(null);

}

public CustomDateDeserializer(Class<?> vc) {

super(vc);

}

@Override

public Date deserialize(

JsonParser jsonparser, DeserializationContext context)

throws IOException {

String date = jsonparser.getText();

try {

return formatter.parse(date);

} catch (ParseException e) {

throw new RuntimeException(e);

}

And here’s the back-to-back test:

@Test

public void whenDeserializingUsingJsonDeserialize_thenCorrect()

throws IOException {

String json

= "{"name":"party","eventDate":"20-12-2014 02:30:00"}";

SimpleDateFormat df

= new SimpleDateFormat("dd-MM-yyyy hh:mm:ss");

Event event = new ObjectMapper()

.readerFor(Event.class)

.readValue(json);

assertEquals(

"20-12-2014 02:30:00", df.format(event.eventDate));

}

4. Jackson Property Inclusion Annotations

4.1. @JsonIgnoreProperties

@JsonIgnoreProperties – one of the most common annotations in Jackson – is used to mark a property or a list of properties to be ignored at the class level.

Let’s go over a quick example ignoring the property id from serialization:

@JsonIgnoreProperties({ "id" })

public class BeanWithIgnore {

public int id;

public String name;

}

And here’s the test making sure the ignore happens:

@Test

public void whenSerializingUsingJsonIgnoreProperties_thenCorrect()

throws JsonProcessingException {

BeanWithIgnore bean = new BeanWithIgnore(1, "My bean");

String result = new ObjectMapper()

.writeValueAsString(bean);

assertThat(result, containsString("My bean"));

assertThat(result, not(containsString("id")));

}

4.2. @JsonIgnore

The @JsonIgnore annotation is used to mark a property to be ignored at the field level.

Let’s use @JsonIgnore to ignore the property id from serialization:

public class BeanWithIgnore {

@JsonIgnore

public int id;

public String name;

}

And the test making sure that id was successfully ignored:

@Test

public void whenSerializingUsingJsonIgnore_thenCorrect()

throws JsonProcessingException {

BeanWithIgnore bean = new BeanWithIgnore(1, "My bean");

String result = new ObjectMapper()

.writeValueAsString(bean);

assertThat(result, containsString("My bean"));

assertThat(result, not(containsString("id")));

}

4.3. @JsonIgnoreType

@JsonIgnoreType is used to mark all properties of an annotated type to be ignored.

Let’s use the annotation to mark all properties of type Name to be ignored:

public class User {

public int id;

public Name name;

@JsonIgnoreType

public static class Name {

public String firstName;

public String lastName;

}

Here’s the simple test making sure the ignore works correctly:

@Test

public void whenSerializingUsingJsonIgnoreType_thenCorrect()

throws JsonProcessingException, ParseException {

User.Name name = new User.Name("John", "Doe");

User user = new User(1, name);

String result = new ObjectMapper()

.writeValueAsString(user);

assertThat(result, containsString("1"));

assertThat(result, not(containsString("name")));

assertThat(result, not(containsString("John")));

}

4.4. @JsonInclude

@JsonInclude is used to exclude properties with empty/null/default values.

Let’s look at an example – excluding nulls from serialization:

@JsonInclude(Include.NON_NULL)

public class MyBean {

public int id;

public String name;

}

Here’s the full test:

public void whenSerializingUsingJsonInclude_thenCorrect()

throws JsonProcessingException {

MyBean bean = new MyBean(1, null);

String result = new ObjectMapper()

.writeValueAsString(bean);

assertThat(result, containsString("1"));

assertThat(result, not(containsString("name")));

}

4.5. @JsonAutoDetect

@JsonAutoDetect is used to override the default semantics of which properties are visible and which are not.

Let’s take a look at how the annotation can be very helpful with a simple example – let’s enable serializing private properties:

@JsonAutoDetect(fieldVisibility = Visibility.ANY)

public class PrivateBean {

private int id;

private String name;

}

And the test:

@Test

public void whenSerializingUsingJsonAutoDetect_thenCorrect()

throws JsonProcessingException {

PrivateBean bean = new PrivateBean(1, "My bean");

String result = new ObjectMapper()

.writeValueAsString(bean);

assertThat(result, containsString("1"));

assertThat(result, containsString("My bean"));

}

5. Jackson Polymorphic Type Handling Annotations

Next – let’s take a look at Jackson polymorphic type handling annotations:

@JsonTypeInfo is used to indicate details of what type information is included in serialization
@JsonSubTypes is used to indicate sub-types of annotated type
@JsonTypeName is used to define logical type name to use for annotated class

Let’s look at a more complex example and use all three – @JsonTypeInfo, @JsonSubTypes, and @JsonTypeName – to serialize/deserialize the entity Zoo:

public class Zoo {

public Animal animal;

@JsonTypeInfo(

use = JsonTypeInfo.Id.NAME,

include = As.PROPERTY,

property = "type")

@JsonSubTypes({

@JsonSubTypes.Type(value = Dog.class, name = "dog"),

@JsonSubTypes.Type(value = Cat.class, name = "cat")

})

public static class Animal {

public String name;

}

@JsonTypeName("dog")

public static class Dog extends Animal {

public double barkVolume;

}

@JsonTypeName("cat")

public static class Cat extends Animal {

boolean likesCream;

public int lives;

}

When we do serialization:

@Test

public void whenSerializingPolymorphic_thenCorrect()

throws JsonProcessingException {

Zoo.Dog dog = new Zoo.Dog("lacy");

Zoo zoo = new Zoo(dog);

String result = new ObjectMapper()

.writeValueAsString(zoo);

assertThat(result, containsString("type"));

assertThat(result, containsString("dog"));

}

Here’s what serializing the Zoo instance with the Dog will result in:

{

"animal": {

"type": "dog",

"name": "lacy",

"barkVolume": 0

}

Now for de-serialization – let’s start with the following JSON input:

{

"animal":{

"name":"lacy",

"type":"cat"

}

And let’s see how that gets unmarshalled to a Zoo instance:

@Test

public void whenDeserializingPolymorphic_thenCorrect()

throws IOException {

String json = "{\"animal\":{\"name\":\"lacy\",\"type\":\"cat\"}}";

Zoo zoo = new ObjectMapper()

.readerFor(Zoo.class)

.readValue(json);

assertEquals("lacy", zoo.animal.name);

assertEquals(Zoo.Cat.class, zoo.animal.getClass());

}

6. Jackson General Annotations

Next – let’s discuss some of Jackson more general annotations.

6.1. @JsonProperty

@JsonProperty is used to indicate the property name in JSON.

Let’s go over the annotation with a simple example – and use @JsonProperty to serialize/deserialize the property name when we’re dealing with non-standard getters and setters:

public class MyBean {

public int id;

private String name;

@JsonProperty("name")

public void setTheName(String name) {

this.name = name;

}

@JsonProperty("name")

public String getTheName() {

return name;

}

Our test:

@Test

public void whenUsingJsonProperty_thenCorrect()

throws IOException {

MyBean bean = new MyBean(1, "My bean");

String result = new ObjectMapper().writeValueAsString(bean);

assertThat(result, containsString("My bean"));

assertThat(result, containsString("1"));

MyBean resultBean = new ObjectMapper()

.readerFor(MyBean.class)

.readValue(result);

assertEquals("My bean", resultBean.getTheName());

}

6.2. @JsonFormat

The @JsonFormat annotation can be used to specify a format when serializing Date/Time values.

In the following example – we use @JsonFormat to control the format of the property eventDate:

public class Event {

public String name;

@JsonFormat(

shape = JsonFormat.Shape.STRING,

pattern = "dd-MM-yyyy hh:mm:ss")

public Date eventDate;

}

And here’s the test:

@Test

public void whenSerializingUsingJsonFormat_thenCorrect()

throws JsonProcessingException, ParseException {

SimpleDateFormat df = new SimpleDateFormat("dd-MM-yyyy hh:mm:ss");

df.setTimeZone(TimeZone.getTimeZone("UTC"));

String toParse = "20-12-2014 02:30:00";

Date date = df.parse(toParse);

Event event = new Event("party", date);

String result = new ObjectMapper().writeValueAsString(event);

assertThat(result, containsString(toParse));

}

6.3. @JsonUnwrapped

@JsonUnwrapped is used for defining values that should be unwrapped/flattened when serialized/deserialized.

Let’s see exactly how that works; we’ll use the annotation to unwrap the property name:

public class UnwrappedUser {

public int id;

@JsonUnwrapped

public Name name;

public static class Name {

public String firstName;

public String lastName;

}

Let’s now serialize an instance of this class:

@Test

public void whenSerializingUsingJsonUnwrapped_thenCorrect()

throws JsonProcessingException, ParseException {

UnwrappedUser.Name name = new UnwrappedUser.Name("John", "Doe");

UnwrappedUser user = new UnwrappedUser(1, name);

String result = new ObjectMapper().writeValueAsString(user);

assertThat(result, containsString("John"));

assertThat(result, not(containsString("name")));

}

Here’s how the output looks like – the fields of the static nested class unwrapped along with the other field:

{

"id":1,

"firstName":"John",

"lastName":"Doe"

}

6.4. @JsonView

@JsonView is used to indicate the View in which the property will be included for serialization/deserialization.

An example will show exactly how that works – we’ll use @JsonView to serialize an instance of Item entity.

Let’s start with the views:

public class Views {

public static class Public {}

public static class Internal extends Public {}

}

And now here’s the Item entity, using the views:

public class Item {

@JsonView(Views.Public.class)

public int id;

@JsonView(Views.Public.class)

public String itemName;

@JsonView(Views.Internal.class)

public String ownerName;

}

Finally – the full test:

@Test

public void whenSerializingUsingJsonView_thenCorrect()

throws JsonProcessingException {

Item item = new Item(2, "book", "John");

String result = new ObjectMapper()

.writerWithView(Views.Public.class)

.writeValueAsString(item);

assertThat(result, containsString("book"));

assertThat(result, containsString("2"));

assertThat(result, not(containsString("John")));

}

6.5. @JsonManagedReference, @JsonBackReference

The @JsonManagedReference and @JsonBackReference annotations are used to handle parent/child relationships and work around loops.

In the following example – we use @JsonManagedReference and @JsonBackReference to serialize our ItemWithRefentity:

public class ItemWithRef {

public int id;

public String itemName;

@JsonManagedReference

public UserWithRef owner;

}

Our UserWithRef entity:

public class UserWithRef {

public int id;

public String name;

@JsonBackReference

public List<ItemWithRef> userItems;

}

And the test:

@Test

public void whenSerializingUsingJacksonReferenceAnnotation_thenCorrect()

throws JsonProcessingException {

UserWithRef user = new UserWithRef(1, "John");

ItemWithRef item = new ItemWithRef(2, "book", user);

user.addItem(item);

String result = new ObjectMapper().writeValueAsString(item);

assertThat(result, containsString("book"));

assertThat(result, containsString("John"));

assertThat(result, not(containsString("userItems")));

}

6.6. @JsonIdentityInfo

@JsonIdentityInfo is used to indicate that Object Identity is to be used when serializing/deserializing values – for instance, to deal with infinite recursion type of problems.

In the following example – we have an ItemWithIdentity entity with a bidirectional relationship with the UserWithIdentity entity:

@JsonIdentityInfo(

generator = ObjectIdGenerators.PropertyGenerator.class,

property = "id")

public class ItemWithIdentity {

public int id;

public String itemName;

public UserWithIdentity owner;

}

And the UserWithIdentity entity:

@JsonIdentityInfo(

generator = ObjectIdGenerators.PropertyGenerator.class,

property = "id")

public class UserWithIdentity {

public int id;

public String name;

public List<ItemWithIdentity> userItems;

}

Now, let’s see how the infinite recursion problem is handled:

@Test

public void whenSerializingUsingJsonIdentityInfo_thenCorrect()

throws JsonProcessingException {

UserWithIdentity user = new UserWithIdentity(1, "John");

ItemWithIdentity item = new ItemWithIdentity(2, "book", user);

user.addItem(item);

String result = new ObjectMapper().writeValueAsString(item);

assertThat(result, containsString("book"));

assertThat(result, containsString("John"));

assertThat(result, containsString("userItems"));

}

Here’s the full output of the serialized item and user:

{

"id": 2,

"itemName": "book",

"owner": {

"id": 1,

"name": "John",

"userItems": [

2

]

}

6.7. @JsonFilter

The @JsonFilter annotation specifies a filter to be used during serialization.

Let’s take a look at an example; first, we define the entity, and we point to the filter:

@JsonFilter("myFilter")

public class BeanWithFilter {

public int id;

public String name;

}

Now, in the full test, we define the filter – which excludes all other properties except name from serialization:

@Test

public void whenSerializingUsingJsonFilter_thenCorrect()

throws JsonProcessingException {

BeanWithFilter bean = new BeanWithFilter(1, "My bean");

FilterProvider filters

= new SimpleFilterProvider().addFilter(

"myFilter",

SimpleBeanPropertyFilter.filterOutAllExcept("name"));

String result = new ObjectMapper()

.writer(filters)

.writeValueAsString(bean);

assertThat(result, containsString("My bean"));

assertThat(result, not(containsString("id")));

}

7. Custom Jackson Annotation

Next – let’s see how to create a custom Jackson annotation; we can make use of the @JacksonAnnotationsInsideannotation – as in the following example:

@Retention(RetentionPolicy.RUNTIME)

@JacksonAnnotationsInside

@JsonInclude(Include.NON_NULL)

@JsonPropertyOrder({ "name", "id", "dateCreated" })

public @interface CustomAnnotation {}

Now, if we use the new annotation on an entity:

@CustomAnnotation

public class BeanWithCustomAnnotation {

public int id;

public String name;

public Date dateCreated;

}

We can see how it does combine the existing annotations into a simpler, custom one that we can use as a shorthand:

@Test

public void whenSerializingUsingCustomAnnotation_thenCorrect()

throws JsonProcessingException {

BeanWithCustomAnnotation bean

= new BeanWithCustomAnnotation(1, "My bean", null);

String result = new ObjectMapper().writeValueAsString(bean);

assertThat(result, containsString("My bean"));

assertThat(result, containsString("1"));

assertThat(result, not(containsString("dateCreated")));

}

The output of the serialization process:

{

"name":"My bean",

"id":1

}

8. Jackson MixIn Annotations

Next – let’s see how to use Jackson MixIn annotations.

Let’s use the MixIn annotations to – for example – ignore properties of type User:

public class Item {

public int id;

public String itemName;

public User owner;

}

1 2	`@JsonIgnoreType` `public` `class` `MyMixInForIgnoreType {}`

Let’s see this in action:

@Test

public void whenSerializingUsingMixInAnnotation_thenCorrect()

throws JsonProcessingException {

Item item = new Item(1, "book", null);

String result = new ObjectMapper().writeValueAsString(item);

assertThat(result, containsString("owner"));

ObjectMapper mapper = new ObjectMapper();

mapper.addMixIn(User.class, MyMixInForIgnoreType.class);

result = mapper.writeValueAsString(item);

assertThat(result, not(containsString("owner")));

}

9. Disable Jackson Annotation

Finally – let’s see how we can disable all Jackson annotations.We can do this by disabling the MapperFeature.USE_ANNOTATIONS as in the following example:

@JsonInclude(Include.NON_NULL)

@JsonPropertyOrder({ "name", "id" })

public class MyBean {

public int id;

public String name;

}

Now, after disabling annotations, these should have no effect and the defaults of the library should apply:

@Test

public void whenDisablingAllAnnotations_thenAllDisabled()

throws IOException {

MyBean bean = new MyBean(1, null);

ObjectMapper mapper = new ObjectMapper();

mapper.disable(MapperFeature.USE_ANNOTATIONS);

String result = mapper.writeValueAsString(bean);

assertThat(result, containsString("1"));

assertThat(result, containsString("name"));

}

The result of serialization before disabling annotations:

1	`{"id":1}`

The result of serialization after disabling annotations:

{

"id":1,

"name":null

}

10. Conclusion

This tutorial has been a deep-dive into Jackson annotations, just scratching the surface of the kind of flexibility you can get using them correctly.

转载：https://www.baeldung.com/jackson-annotations

Jackson Annotation Examples的更多相关文章

练习：将值是null的数据删除掉（剔除）:com.fasterxml.jackson.annotation.JsonInclude;包
练习:将值是null的数据删除掉(剔除):com.fasterxml.jackson.annotation.JsonInclude;包例如,有数据是null,不想展示 { "statusC ...
fastxml Jackson annotation使用小记
dependencies: compile("com.fasterxml.jackson.core:jackson-annotations") compile("com. ...
NoClassDefFound Error: com/fasterxml/jackson/annotation/JsonAutoDetect
少了 jackson-annotation https://blog.csdn.net/qq_36497454/article/details/80461676
Jackson替换fastjson
为什么要替换fastjson 工程里大量使用了fastjson作为序列化和反序列化框架,甚至ORM在处理部分字段也依赖fastjson进行序列化和反序列化.那么作为大量使用的基础框架,为什么还要进行替 ...
Create JSON by Jackson API（转）
原文地址: Create JSON by Jackson API Jackson API is a multi-purpose Java library for processing JSON. ...
【jackson 异常】com.fasterxml.jackson.databind.JsonMappingException异常处理
项目中,父层是Gene.java[基因实体] 子层是Corlib.java[文集库实体],一种基因对用多个文集库文章但是在查询文集库这个实体的时候报错:[com.fasterxml.jackson ...
使用 jackson 解析 json 演示样例
首先须要下载3个包,下载地址在Github FasterXML,这三个核心模块各自是: Streaming ("jackson-core") defines low-level s ...
Java下利用Jackson进行JSON解析和序列化
Java下利用Jackson进行JSON解析和序列化 Java下常见的Json类库有Gson.JSON-lib和Jackson等,Jackson相对来说比较高效,在项目中主要使用Jackson进行 ...
jackson annotations注解详解 (zhuan)
http://blog.csdn.net/sdyy321/article/details/40298081 ************************************** 官方WIKI: ...

随机推荐

TED学习笔记
20180621(如何做得更好) 多一些探索,询问,聆听,奋斗,成就自己,比一味的做事儿有效的多. 1.刻意让自己的生活在两个区域交替:(1)学习区Learning Zero (2)执行区Perfor ...
LOJ #556. 「Antileaf's Round」咱们去烧菜吧
好久没更博了咕咕咕现在多项式板子的常数巨大...周末好好卡波常吧.... LOJ #556 题意给定$ m$种物品的出现次数$ B_i$以及大小$ A_i$ 求装满大小为$[1..n]$的背包的 ...
找不到或无法加载主类（Could not find or load main class）
一般可能会是包名引起的,还有可能就不小心加上了.class后缀解决方案如下可以加上目录或者使用符号 . ,注意要用空格隔开 java -cp d:\sample HelloWorldjava -c ...
Android获取虚拟软键盘高度
public static int getDpi(Context context) { int dpi = 0; WindowManager windowManager = (WindowManage ...
web开发简史与技术选型
视频地址:http://v.youku.com/v_show/id_XMTQxNzM1MzAwOA==.html?firsttime=0&from=y1.4-2
【原创】大数据基础之Zookeeper（4）应用场景
1 集群配置管理应用服务器的配置通常会放到properties文件中,格式为: system1.module2.prop3=value4 然后启动的时候加载,这样带来的问题是启动后无法修改,想修改必 ...
转载一篇好理解的vue ssr文章
转载:原文链接https://www.86886.wang/detail/5b8e6081f03d630ba8725892,谢谢作者的分享前言大多数Vue项目要支持SSR应该是为了SEO考虑,毕竟 ...
Mac 安装JRE 1.8
最近使用React Native,运行android版本时,需要jre 1.8,但是用oracle 的安装文件安装完毕后,在控制台java -version输出的还是 1.7版本.发现是环境变量没配对 ...
laravel whereDoesntHave
select * from `feeds` where not exists (select * from `black_lists` where `feeds`.`user_id` = `black ...
金蝶KIS&K3助记码SQL数据库批量刷新
金蝶KIS&K3助记码SQL数据库批量刷新用的次数不多,就没有写入存储过程或者触发里面了,可以自行实现. 第一步选择对应账套的数据库,执行下面的命令,这个是一个函数. go if exist ...

Jackson Annotation Examples

1. Overview

Further reading:

More Jackson Annotations

Jackson – Bidirectional Relationships

Getting Started with Custom Deserialization in Jackson

2. Jackson Serialization Annotations

2.1. @JsonAnyGetter

2.2. @JsonGetter

2.3. @JsonPropertyOrder

2.4. @JsonRawValue

2.5. @JsonValue

2.6. @JsonRootName

2.7. @JsonSerialize

3. Jackson Deserialization Annotations

3.1. @JsonCreator

3.2. @JacksonInject

3.3. @JsonAnySetter

3.4. @JsonSetter

3.5. @JsonDeserialize

4. Jackson Property Inclusion Annotations

4.1. @JsonIgnoreProperties

4.2. @JsonIgnore

4.3. @JsonIgnoreType

4.4. @JsonInclude

4.5. @JsonAutoDetect

5. Jackson Polymorphic Type Handling Annotations

6. Jackson General Annotations

6.1. @JsonProperty

6.2. @JsonFormat

6.3. @JsonUnwrapped

6.4. @JsonView

6.5. @JsonManagedReference, @JsonBackReference

6.6. @JsonIdentityInfo

6.7. @JsonFilter

7. Custom Jackson Annotation

8. Jackson MixIn Annotations

9. Disable Jackson Annotation

10. Conclusion

Jackson Annotation Examples的更多相关文章

随机推荐

热门专题