


How SpringBoot implements unified encapsulation and returns the front-end result set
How do we encapsulate this result? We should pay attention to the information contained in the data returned to the front end.
Generally speaking, first of all, this time there must be a code to represent the status of the interface. For example, 0 means success, 1 means failure, 2 means wrong parameters had to be passed, 4 means system exception, and so on. This is just a simple example. Many people may have questions. The HTTP protocol itself already has corresponding return code definitions. For example: 200 means success, 500 means server error, 404 means page not found.
For example, 200 indicates that the request was successful, but it cannot describe the business results in the request. For example, the username already exists, in fact, the business is not successful, but the HTTP result is definitely 200, so we need a code to describe our business status.
In addition to the code, there are also some prompt messages, such as successful operation, system exception, user name already exists, etc., so we added a message field.
In addition, there is our core data. For example, I'm getting data based on ID. The specific content of this data must be returned to the front end, so there must be data. What type is used for this data? This type must be diverse, so we need to use a unified parent class so that the object can receive all types. Of course, we can use some general methods to facilitate operation.
Then there is our core data. For example, I'm getting data based on ID. The specific content of this data must be returned to the front end, so there must be data. What type is used for this data? This type must be diverse, so we need to use a unified parent class so that the object can receive all types. Of course, we can use general methods to facilitate operation.
Main code display:
public class Result<T> implements Serializable { private static final long serialVersionUID = -3960261604608758516L; private int code; private String msg; private T data; public static <T> Result<T> success() { return new Result<>(); } /** * 成功,默认状态码,返回消息,自定义返回数据 * @param data 自定义返回数据 * @param <T> 返回类泛型,不能为String * @return 通用返回Result */ public static <T> Result<T> success(T data) { return new Result<>(data); } /** * 成功,默认状态码,自定义返回消息,返回数据 * @param msg 自定义返回消息 * @param data 自定义返回数据 * @param <T> 返回类泛型 * @return 通用返回Result */ public static <T> Result<T> success(String msg, T data) { return new Result<>(msg, data); } /** * 成功,默认状态码,自定义返回消息,无返回数据 * * @param msg 自定义返回消息 * @param <T> 返回类泛型 * @return 通用返回Result */ public static <T> Result<T> success(String msg) { return new Result<>(msg); } /** * 失败,默认状态码,返回消息,无返回数据 * @param <T> 返回类泛型 * @return 通用返回Result */ public static <T> Result<T> error() { return new Result<>(ResultCode.ERROR); } /** * 失败,默认状态码,自定义返回消息,无返回数据 * @param <T> 返回类泛型 * @return 通用返回Result */ public static <T> Result<T> error(String msg) { return new Result<>(ResultCode.ERROR.getCode(), msg); } /** * 失败,自定义状态码,返回消息,无返回数据 * @param code 自定义状态码 * @param msg 自定义返回消息 * @param <T> 返回类泛型 * @return 通用返回Result */ public static <T> Result<T> error(int code, String msg) { return new Result<>(code, msg); } /** * 失败,使用CodeMsg状态码,返回消息,无返回数据 * @param resultCode CodeMsg,参数如下: * <p> code 状态码 * <p> msg 返回消息 * @param <T> 返回类泛型 * @return 通用返回Result */ public static <T> Result<T> error(ResultCode resultCode) { return new Result<>(resultCode); } /** * 成功构造器,无返回数据 */ private Result() { this(ResultCode.SUCCESS); } /** * 成功构造器,自定义返回数据 * @param data 返回数据 */ private Result(T data) { this(ResultCode.SUCCESS, data); } /** * 成功构造器,自定义返回消息,无返回数据 * @param msg 返回消息 */ private Result(String msg) { this(ResultCode.SUCCESS.getCode(), msg); } /** * 构造器,自定义状态码,返回消息 * @param code 状态码 * @param msg 返回消息 */ private Result(int code, String msg) { this.code = code; this.msg = msg; } /** * 成功构造器,自定义返回信息,返回数据 * @param msg 返回信息 * @param data 返回数据 */ private Result(String msg, T data) { this(ResultCode.SUCCESS.getCode(), msg, data); } /** * 构造器,自定义状态码,返回消息,返回数据 * @param code 状态码 * @param msg 返回消息 * @param data 返回数据 */ private Result(int code, String msg, T data) { this(code, msg); this.data = data; } /** * 构造器,使用CodeMsg状态码与返回信息,自定义返回数据 * @param resultCode CodeMsg,参数如下: * <p> code 状态码 * <p> msg 返回消息 * @param data 返回数据 */ private Result(ResultCode resultCode, T data) { this(resultCode); this.data = data; } /** * 构造器,使用CodeMsg状态码与返回信息 * @param resultCode CodeMsg,参数如下: * <p> code 状态码 * <p> msg 返回消息 */ private Result(ResultCode resultCode) { this(resultCode.getCode(), resultCode.getMsg()); } }
You also need to define several common errors
@Builder public class ResultCode implements Serializable { private static final long serialVersionUID = -6269841958947880397L; /** 状态码*/ private int code; /**状态信息*/ private String msg; /** 默认成功*/ public final static ResultCode SUCCESS = dispose(ResultCodeEnum.SUCCESS); /**默认失败*/ public final static ResultCode ERROR = dispose(ResultCodeEnum.ERROR); /**通用业务异常*/ public final static ResultCode BIZ_ERROR = dispose(ResultCodeEnum.BIZ_ERROR); /**文件超出最大限制*/ public final static ResultCode FILE_OUT_MAX = dispose(ResultCodeEnum.FILE_OUT_MAX); /**文件格式不正确*/ public final static ResultCode FILE_FORMAT_ERROR = dispose(ResultCodeEnum.FILE_FORMAT_ERROR); /** 参数错误*/ public final static ResultCode PARAM_ERROR = dispose(ResultCodeEnum.PARAM_ERROR); /**Json解析异常*/ public final static ResultCode JSON_FORMAT_ERROR = dispose(ResultCodeEnum.JSON_FORMAT_ERROR); /** Sql解析异常*/ public final static ResultCode SQL_ERROR = dispose(ResultCodeEnum.SQL_ERROR); /**网络超时*/ public final static ResultCode NETWORK_TIMEOUT = dispose(ResultCodeEnum.NETWORK_TIMEOUT); /** 未知的接口*/ public final static ResultCode UNKNOWN_INTERFACE = dispose(ResultCodeEnum.UNKNOWN_INTERFACE); /**请求方式不支持*/ public final static ResultCode REQ_MODE_NOT_SUPPORTED = dispose(ResultCodeEnum.REQ_MODE_NOT_SUPPORTED); /**系统异常*/ public final static ResultCode SYS_ERROR = dispose(ResultCodeEnum.SYS_ERROR); private static ResultCode dispose(ResultCodeEnum codeEnum) { return ResultCode.builder().code(codeEnum.getCode()).msg(codeEnum.getMsg()).build(); } public ResultCode(int code, String msg) { this.code = code; this.msg = msg; } }
The above is the detailed content of How SpringBoot implements unified encapsulation and returns the front-end result set. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



Introduction to Jasypt Jasypt is a java library that allows a developer to add basic encryption functionality to his/her project with minimal effort and does not require a deep understanding of how encryption works. High security for one-way and two-way encryption. , standards-based encryption technology. Encrypt passwords, text, numbers, binaries... Suitable for integration into Spring-based applications, open API, for use with any JCE provider... Add the following dependency: com.github.ulisesbocchiojasypt-spring-boot-starter2. 1.1Jasypt benefits protect our system security. Even if the code is leaked, the data source can be guaranteed.

Usage scenario 1. The order was placed successfully but the payment was not made within 30 minutes. The payment timed out and the order was automatically canceled. 2. The order was signed and no evaluation was conducted for 7 days after signing. If the order times out and is not evaluated, the system defaults to a positive rating. 3. The order is placed successfully. If the merchant does not receive the order for 5 minutes, the order is cancelled. 4. The delivery times out, and push SMS reminder... For scenarios with long delays and low real-time performance, we can Use task scheduling to perform regular polling processing. For example: xxl-job Today we will pick

1. Redis implements distributed lock principle and why distributed locks are needed. Before talking about distributed locks, it is necessary to explain why distributed locks are needed. The opposite of distributed locks is stand-alone locks. When we write multi-threaded programs, we avoid data problems caused by operating a shared variable at the same time. We usually use a lock to mutually exclude the shared variables to ensure the correctness of the shared variables. Its scope of use is in the same process. If there are multiple processes that need to operate a shared resource at the same time, how can they be mutually exclusive? Today's business applications are usually microservice architecture, which also means that one application will deploy multiple processes. If multiple processes need to modify the same row of records in MySQL, in order to avoid dirty data caused by out-of-order operations, distribution needs to be introduced at this time. The style is locked. Want to achieve points

Springboot reads the file, but cannot access the latest development after packaging it into a jar package. There is a situation where springboot cannot read the file after packaging it into a jar package. The reason is that after packaging, the virtual path of the file is invalid and can only be accessed through the stream. Read. The file is under resources publicvoidtest(){Listnames=newArrayList();InputStreamReaderread=null;try{ClassPathResourceresource=newClassPathResource("name.txt");Input

When Springboot+Mybatis-plus does not use SQL statements to perform multi-table adding operations, the problems I encountered are decomposed by simulating thinking in the test environment: Create a BrandDTO object with parameters to simulate passing parameters to the background. We all know that it is extremely difficult to perform multi-table operations in Mybatis-plus. If you do not use tools such as Mybatis-plus-join, you can only configure the corresponding Mapper.xml file and configure The smelly and long ResultMap, and then write the corresponding sql statement. Although this method seems cumbersome, it is highly flexible and allows us to

SpringBoot and SpringMVC are both commonly used frameworks in Java development, but there are some obvious differences between them. This article will explore the features and uses of these two frameworks and compare their differences. First, let's learn about SpringBoot. SpringBoot was developed by the Pivotal team to simplify the creation and deployment of applications based on the Spring framework. It provides a fast, lightweight way to build stand-alone, executable

1. Customize RedisTemplate1.1, RedisAPI default serialization mechanism. The API-based Redis cache implementation uses the RedisTemplate template for data caching operations. Here, open the RedisTemplate class and view the source code information of the class. publicclassRedisTemplateextendsRedisAccessorimplementsRedisOperations, BeanClassLoaderAware{//Declare key, Various serialization methods of value, the initial value is empty @NullableprivateRedisSe

In projects, some configuration information is often needed. This information may have different configurations in the test environment and the production environment, and may need to be modified later based on actual business conditions. We cannot hard-code these configurations in the code. It is best to write them in the configuration file. For example, you can write this information in the application.yml file. So, how to get or use this address in the code? There are 2 methods. Method 1: We can get the value corresponding to the key in the configuration file (application.yml) through the ${key} annotated with @Value. This method is suitable for situations where there are relatively few microservices. Method 2: In actual projects, When business is complicated, logic
