Many people are using spring to develop java projects, but when configuring maven dependencies, it is not clear which spring jars to configure. They often add a bunch of them randomly, and then continue to configure the jar dependencies when compilation or running errors are reported, resulting in confusion of spring dependencies, or even downloading. When creating the same type of project at a time, I don’t know which spring dependencies to configure, I can only copy them. In fact, that’s what I did at the beginning!
There are only about 20 jar packages in spring, each with corresponding functions. One jar may also depend on several other jars. Therefore, it is concise and clear to understand the relationship between them and configure maven dependencies. Here is an example: To use the spring framework in ordinary java projects, what jars are needed? Just one
<dependency> <groupid>org.springframework</groupid> <artifactid>spring-context</artifactid> <version>3.2.17.RELEASE</version> </dependency>
What about introducing spring mvc into web projects? Just configure a dependency
<dependency> <groupid>org.springframework</groupid> <artifactid>spring-webmvc</artifactid> <version>3.2.17.RELEASE</version> </dependency>
Why can it be configured like this? Next, we take the spring 3.2.17.RELEASE version as an example to introduce the spring framework structure. Spring 4 is slightly different and will be introduced at the end
The spring official website gives a structure diagram of spring3
The picture divides spring into 5 parts: core, aop, data access, web, and test. Each rounded rectangle in the picture corresponds to a jar. If configured in maven, the "groupId" of all these jars is "org" .springframework", each jar has a different "artifactId", in addition, "instrumentation" has two jars, and a "spring-context-support" is not listed in the figure, so there are 19 jar packages for spring3 in total.
The following introduces the jars and dependencies of these five parts
core
The core part contains 4 modules
spring-core: The most basic implementation of dependency injection IoC and DI
spring-beans: Bean factory and bean assembly
spring-context: spring's context context is the IoC container
spring-expression: spring expression language
Their complete dependencies
Because spring-core relies on commons-logging, and other modules rely on spring-core, the entire spring framework relies on commons-logging. If you have your own log implementation such as log4j, you can eliminate the dependence on commons-logging. No Log implementation excludes commons-logging dependency, compilation error
<dependency> <groupid>org.springframework</groupid> <artifactid>spring-context</artifactid> <version>3.2.17.RELEASE</version> <exclusions> <exclusion> <groupid>commons-logging</groupid> <artifactid>commons-logging</artifactid> </exclusion> </exclusions> </dependency>
aop
The aop part contains 4 modules
spring-aop: aspect-oriented programming
spring-aspects: Integrate AspectJ
spring-instrument: Provides some class-level tool support and ClassLoader-level implementation for server
spring-instrument-tomcat: instrument implementation for tomcat
Their dependencies
data access
The data access part contains 5 modules
spring-jdbc: jdbc support
spring-tx: transaction control
spring-orm: object relational mapping, integrated orm framework
spring-oxm: object xml mapping
spring-jms:java message service
Their dependencies
web
The web part contains 4 modules
spring-web: basic web functions, such as file upload
spring-webmvc: mvc implementation
spring-webmvc-portlet: portlet-based mvc implementation
spring-struts: Integration with struts, not recommended, spring4 no longer provides
Their dependencies
test
There is only one module in the test part. I will also put spring-context-support here
spring-test: spring test, providing junit and mock testing functions
spring-context-support: spring additional support packages, such as mail service, view analysis, etc.
Their dependencies
This is the end of the introduction to spring 3. Looking at these pictures, I believe you will no longer be confused when configuring spring dependencies in maven.
The following introduces spring4, which is basically the same structure as spring3. The following is the structure diagram given by the official website
As you can see, the struts of spring3 have been removed from the picture, messaging and websocket have been added, and other modules remain unchanged. Therefore, there are 20 jars of spring4
spring-websocket: An efficient communication tool for web applications
spring-messaging: for building messaging-based applications
Their dependencies
The above is the detailed content of Spring core framework architecture. For more information, please follow other related articles on the PHP Chinese website!

Java is widely used in enterprise-level applications because of its platform independence. 1) Platform independence is implemented through Java virtual machine (JVM), so that the code can run on any platform that supports Java. 2) It simplifies cross-platform deployment and development processes, providing greater flexibility and scalability. 3) However, it is necessary to pay attention to performance differences and third-party library compatibility and adopt best practices such as using pure Java code and cross-platform testing.

JavaplaysasignificantroleinIoTduetoitsplatformindependence.1)Itallowscodetobewrittenonceandrunonvariousdevices.2)Java'secosystemprovidesusefullibrariesforIoT.3)ItssecurityfeaturesenhanceIoTsystemsafety.However,developersmustaddressmemoryandstartuptim

ThesolutiontohandlefilepathsacrossWindowsandLinuxinJavaistousePaths.get()fromthejava.nio.filepackage.1)UsePaths.get()withSystem.getProperty("user.dir")andtherelativepathtoconstructthefilepath.2)ConverttheresultingPathobjecttoaFileobjectifne

Java'splatformindependenceissignificantbecauseitallowsdeveloperstowritecodeonceandrunitonanyplatformwithaJVM.This"writeonce,runanywhere"(WORA)approachoffers:1)Cross-platformcompatibility,enablingdeploymentacrossdifferentOSwithoutissues;2)Re

Java is suitable for developing cross-server web applications. 1) Java's "write once, run everywhere" philosophy makes its code run on any platform that supports JVM. 2) Java has a rich ecosystem, including tools such as Spring and Hibernate, to simplify the development process. 3) Java performs excellently in performance and security, providing efficient memory management and strong security guarantees.

JVM implements the WORA features of Java through bytecode interpretation, platform-independent APIs and dynamic class loading: 1. Bytecode is interpreted as machine code to ensure cross-platform operation; 2. Standard API abstract operating system differences; 3. Classes are loaded dynamically at runtime to ensure consistency.

The latest version of Java effectively solves platform-specific problems through JVM optimization, standard library improvements and third-party library support. 1) JVM optimization, such as Java11's ZGC improves garbage collection performance. 2) Standard library improvements, such as Java9's module system reducing platform-related problems. 3) Third-party libraries provide platform-optimized versions, such as OpenCV.

The JVM's bytecode verification process includes four key steps: 1) Check whether the class file format complies with the specifications, 2) Verify the validity and correctness of the bytecode instructions, 3) Perform data flow analysis to ensure type safety, and 4) Balancing the thoroughness and performance of verification. Through these steps, the JVM ensures that only secure, correct bytecode is executed, thereby protecting the integrity and security of the program.


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

WebStorm Mac version
Useful JavaScript development tools

Safe Exam Browser
Safe Exam Browser is a secure browser environment for taking online exams securely. This software turns any computer into a secure workstation. It controls access to any utility and prevents students from using unauthorized resources.

VSCode Windows 64-bit Download
A free and powerful IDE editor launched by Microsoft

Dreamweaver CS6
Visual web development tools

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software
