Shulou(Shulou.com)06/02 Report--

This article shows you how to parse Java entity classes to achieve chain operations, the content is concise and easy to understand, can definitely brighten your eyes, through the detailed introduction of this article, I hope you can get something.

This is how bean is written, simply using get and set methods, plus a toString.

Package Model;/** * @ author: Davion * @ date: 2019-12-11 * @ description: * / public class User {private Integer id; private String name; @ Override public String toString () {return "User {" + "id=" + id + ", name='" + name +'\'+'}';} public Integer getId () {return id;} public void setId (Integer id) {this.id = id;} public String getName () {return name } public void setName (String name) {this.name = name;}}

And then the use is constant set.

Import Model.User;/** * @ author: Davion * @ date: 2019-12-11 * @ description: * / public class Main {public static void main (String [] args) {User user = new User (); user.setId (1); user.setName ("Davion"); System.out.println (user);}}

Even more simple is to use Lombok to automatically produce get/set. Of course, we are not talking about the advantages of Lombok today, although it is really easy to use.

But today I suddenly saw some new operations: chained bean, as follows

Modify the User class as follows:

Package Model;/** * @ author: Davion * @ date: 2019-12-11 * @ description: * / public class User {private Integer id; private String name; @ Override public String toString () {return "User {" + "id=" + id + ", name='" + name +'\'+'}';} public Integer getId () {return id;} public User setId (Integer id) {this.id = id; return this;} public String getName () {return name } public User setName (String name) {this.name = name; return this;}}

As you can see, the difference with the original is that the set method is modified. Originally, there is no return value, but a property is set directly, but now the return type is the model province, and the return value is this.

Here's the point, and then when the client uses it, it looks like this:

Import Model.User;/** * @ author: Davion * @ date: 2019-12-11 * @ description: * / public class Main {public static void main (String [] args) {User user = new User (); user.setId (1). SetName ("Davion"); System.out.println (user);}}

Because the return object is this, you can then use all the methods of the current model

This chain operation saves a lot of time, is intuitive and concise, and has no effect on the original way of writing.

Because I usually use Lombok, I don't write get/set methods myself, so how can chain operations be implemented using Lombok?

As we all know, Lombok uses annotations to make the code more concise, so if you want Lombok to implement chained bean, you should also use corresponding annotations.

This annotation is @ Accessors (chain = true), meaning that the accessor allows chained operations, so now the code is:

Package Model;import lombok.Data;import lombok.experimental.Accessors;/** * @ author: Davion * @ date: 2019-12-11 * @ description: * / @ Accessors (chain = true) @ Datapublic class User {private Integer id; private String name;}

The client code does not need to change, so a chained bean is implemented.

The above is how to parse Java entity classes to implement chain operations. Have you learned any knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.