About the source code
Learned: http://www.newsmth.net/bbscon.php?bid=756&id=415935
Have a look at the source code. 1. Will verify some design viewpoints, such as interface-oriented programming, low coupling, high cohesion, modularity, KISS, etc. 2. In terms of tool classes, you can expand your knowledge points and deepen your understanding, such as collections, strings, properties, instantiation of classes, classloader, etc., which can make up for your ill-consideration before. 3. Specific to some spring modules, you can learn how spring is integrated and implemented. For example, spring mvc, you can understand various strategies and details such as servlet request-to-c mapping, parameter (data) binding and verification, v parsing, and v rendering. You can learn how spring mvc integrates various third-party solutions, and you can learn how spring mvc implements itself. Modules similar to spring mvc, such as orm, database transaction processing, etc., can actually deepen the understanding of this aspect. 4. The early spring focused on integrating third-party libraries, but after spring boot, it seems that spring boot "redefined" how to use spring, and how to quickly develop and deploy java programs. Learning the source code, you can understand how spring boot uses spring, and how spring boot is developed quickly. 5. Spring integrates many third-party libraries. If you have the energy, you can learn these third-party libraries one by one. After all, spring can look at it, and it’s not much worse. 6, the most basic, you can understand how to implement an ioc, aop framework.