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

This article mainly explains "springmvc implementation of input and output information printing log", interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Next let the editor to take you to learn "springmvc to achieve input and output information printing log" bar!

Preface

Colleagues add log output of input parameters, log output of output data or aop mode to all controller methods. It's really annoying, bird dish, ah, give everyone a simple way.

First, manually add log printing method @ Slf4j@RestControllerpublic class UserController {@ RequestMapping ("getUserInfo") public UserInfo getUserInfo (Long userId) {log.info ("- > query getUserInfo input parameter {}", id); xxxxxxxx log.info ("- > query getUserInfo output {}", xxx) } @ RequestMapping ("newGetUserInfo") public UserInfo getUserInfo (Long userId, Long appId) {log.info ("- > query getUserInfo input parameters id: {}, appId: {}", id, appId); xxxxxxxx log.info ("- > query getUserInfo output {}", xxxx) }} problem

Each class needs to be annotated with @ Slf4j, which is not a big problem. If you don't need to print, then you don't have to. It's annoying to have an alarm.

Each method declaration has to write input and output code before return, which is a lot of work.

Multiple input parameters, printing is very troublesome, adding one input parameter needs to be modified, the workload is heavy, and it is easy to make mistakes

The method name must be added to the input and output string, which is a lot of work. It's annoying that you also need to modify the method when you copy it. It is easy to make an error when adding a method name, but forget to modify it when you modify it. Easy to make mistakes

Log level is not easy to control, must be info level, otherwise many other debug logs will be printed, because it is info level, when you want to close the input and output, because there are a lot of key information printed to the log through the info level, it cannot be closed.

If the output is printed using the debug level, when the directory of the controller is different, the log level of the controller needs to be debug in the configuration of the log file. Easy to forget the configuration, accidents, the online is generally closed.

Summary

The workload is heavy, the code is not elegant (ugly), the log information and configuration are prone to errors, and the configuration is difficult to manage.

Aop implementation

Baidu randomly find a spring aop to achieve log output, please click on the Spring AOP to achieve unified log output. Is to repeat the wheel without wanting to be evil.

problem

Unified log output needs to be implemented based on Spring AOP, and it is very robust and has no problem. And very strong, no problem. And very strong, no problem.

Need to start Spring AOP to achieve unified log output

The aspect of aop needs to be configured. If the controller directory is different, it is easy to make mistakes if you need to add and modify aspect points.

If it is not based on jar dependency, you need to copy the Spring AOP unified log output code for each project, which is super troublesome and error-prone.

When your Spring AOP implements uniform log output and changes, you need to modify all the project jar dependencies. If it is the way to copy the code, it will be more troublesome.

If you are dependent on jar, you need one more dependency, and it is very bad to be a cleanliness addict. If it is through the code, there may be no need to modify the code, there will be an aop directory in the project directory, bird vegetables will be bored to death, in the business code. Only those business directories, functional directories should not appear. And try to keep the directory simple.

Summary

Management is very troublesome, error-prone, need a certain degree of programmer maintenance, high cost, high cost.

The solution of bird vegetable.

The first step is to introduce dependency

Org.slf4j slf4j-api ch.qos.logback logback-core ch.qos.logback logback-access Ch.qos.logback logback-classic org.slf4j jcl-over-slf4j

Step 2 configure input and output

The third step depends on the effect.

2019-10-21 12 Invoking 02 http-nio-12140-exec-2 [http-nio-12140-exec-2] TRACEo.s.w.s.m.m.a.ServletInvocableHandlerMethod-Invoking 'com.xxx.UserController.getUserInfo' with arguments [1] 2019-10-21 12 Fringe 02Lux 18.920 [http-nio-12140-exec-2] TRACEo.s.w.s.m.m.a.ServletInvocableHandlerMethod-Method [com.xxx.UserController.getUserInfo] returned [xxxx] shortcomings

The printed data is a little long.

There is no way to synthesize multiple log outputs into one

Either close it or open it together, there is no way to be flexible.

Advantages

grace

simple

No invasion

At this point, I believe that everyone on the "springmvc implementation of input and output information printing log" have a deeper understanding, might as well to the actual operation of it! Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

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.