Storing bean objects
When we stored bean objects before, we needed to add a line of beans to the configuration file to inject them
This injection method is not good. If there is an error in the configuration file, the program will not display the error message. This is very unfriendly to beginners.
1. Create a project
Create startup class and main method
Introduce dependencies
<dependencies> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-context</artifactId> <version>5.2.3.RELEASE</version> </dependency> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-beans</artifactId> <version>5.2.3.RELEASE</version> </dependency> </dependencies>
Create configuration file
We agreed that the bean object to be created will be placed under the com.bean package:
<dependencies> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-context</artifactId> <version>5.2.3.RELEASE</version> </dependency> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-beans</artifactId> <version>5.2.3.RELEASE</version> </dependency> </dependencies>
2. Add annotations to store beans in the container
The core of using Spring is to use annotations. There are 5 annotations we have learned.
@Controller [Controller] @Service [Service] @Repository [Warehouse] @Configuration [Configuration/Layout] @Component [Component] 2.1 controller
We were able to get the object by passing in the id parameter before, but that was adding a line of beans to manually add the id, but now that we use annotations, can we only use class types? Get it?
When we use annotations to inject bean objects, the id actually defaults to the camel case form of the class name:
The reason will not be explained first. , will be discussed later.
Easy mistakes
:
We previously added the root directory for bean object search in the configuration file, which means that the search will start from this directory downwards, but not upwards :
Lower-level directory
##Superior directory
##2.2 Service
#2.3 Repository
##2.5 Component
2.6 Why are there 5 major categories of annotations
in the company Everyone is responsible for different areas, so the class annotations used are also different, but the essence of the five major categories of annotations is the same.
We can clearly see through the two class annotations that the other four annotations are methods that introduce the Component annotation. In other words, Component is the father of the other four class annotations. So what does Component do? It’s just that it’s not easy to throw it into the other four classes when annotating it~
2.7 Why does the id default to a small camel number
Find AnnotationBeanNameGenerator:
##Test:
##2.8.2 Rename multiple
: When renaming using the name attribute, the original method name will lose its effect, which means that only the modified one can be used The name is used as the ID. Get the bean object
- Property injection
- Constructor injection
- Setter injection
- 1. Property injection
1.1 Autowired
##Although there seems to be no problem now, when we Objects of the same type have been injected multiple times:
At this time, you need to accurately locate the selected object. Type name
Resource has a name attribute, which can specify the name of the injected bean
ps: The Autowired annotation initially queries all types for the types of objects that need to be injected. However, Autowired can only inject one object at a time, so an error will be reported when an object of the same type is injected multiple times. The Qualifier annotation essentially filters the results of its query.
2. Constructor injection
: When there is only one constructor, Autowired can be omitted
Setter injection
or through Autowired
## Resource also supports Setter injection.
What are the differences between property injection, constructor injection, and Setter injection?
The above is the detailed content of Example analysis of read and write operations in Java Spring. 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

MantisBT
Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.

WebStorm Mac version
Useful JavaScript development tools

SecLists
SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.

SAP NetWeaver Server Adapter for Eclipse
Integrate Eclipse with SAP NetWeaver application server.

Dreamweaver Mac version
Visual web development tools
