


This article brings you an introduction to the three core annotations of Spring Boot (with code). It has certain reference value. Friends in need can refer to it. I hope it will be helpful to you.
I recently interviewed some Java developers. Some of them have actually used Spring Boot in the company, and some have learned it in their spare time as a hobby. However, when I asked them what the three core annotations of Spring Boot were, I was disappointed that few people could answer them. In this way, can you say that you know Spring Boot very well? This may also cost you points!
Explanation of Spring Boot core annotations
The biggest feature of Spring Boot is that it does not require XML configuration files, can automatically scan the package path to load and inject objects, and can do it according to the classpath The jar package under is automatically configured.
So the three core annotations of Spring Boot are:
1, @Configuration
org.springframework.context.annotation.Configuration
This is an annotation added by Spring 3.0 to replace the applicationContext.xml configuration file. All things that can be done in this configuration file can be registered through the class where this annotation is located.
The following related considerations are also very important!
@Bean
is used to replace the
@ImportResource
If some cannot be configured through class registration, you can introduce additional XML configuration files through this annotation. Some old configuration files cannot be passed@Configuration
The configuration method is very useful.
@Import
Used to introduce one or more additional @Configuration modified configuration file classes.
@SpringBootConfiguration
This annotation is a variant of the @Configuration annotation. It is only used to modify the Spring Boot configuration, or to facilitate the subsequent expansion of Spring Boot. Source code as follows.
@Target(ElementType.TYPE) @Retention(RetentionPolicy.RUNTIME) @Documented @Configuration public @interface SpringBootConfiguration { }
2, @ComponentScan
org.springframework.context.annotation.ComponentScan
This is an annotation added by Spring 3.1 to replace The component-scan configuration in the configuration file turns on component scanning, that is, it automatically scans the @Component annotation under the package path to register the bean instance into the context.
In addition, @ComponentScans is a repeatable annotation, that is, multiple annotations can be configured to configure and register different sub-packages.
3, @EnableAutoConfiguration
org.springframework.boot.autoconfigure.EnableAutoConfiguration
You can tell by looking at the full path, this is since the birth of Spring Boot The added annotations are used to provide automatic configuration. The above two are under the spring-context
package and do not belong to Spring Boot. Therefore, the XML configuration method after Spring 3.0 has been laid down for Spring Boot. Foreshadowing!
For more detailed usage and actual combat of automatic configuration, please read this article "Spring Boot Automatic Configuration Principles and Practical Combat".
The last easter egg
Now that the three core annotations of Spring Boot have been introduced, you may have questions, why is the most important annotation @SpringBootApplication not among them?
An Easter egg for everyone, in fact, this @SpringBootApplication annotation contains the above three main annotations. If there is no need for custom configuration, just use the @SpringBootApplication annotation!
Let us take a look at the source code of the @SpringBootApplication annotation, everything is clear!
@Target(ElementType.TYPE) @Retention(RetentionPolicy.RUNTIME) @Documented @Inherited @SpringBootConfiguration @EnableAutoConfiguration @ComponentScan(excludeFilters = { @Filter(type = FilterType.CUSTOM, classes = TypeExcludeFilter.class), @Filter(type = FilterType.CUSTOM, classes = AutoConfigurationExcludeFilter.class) }) public @interface SpringBootApplication { ... }
The above is the detailed content of Introduction to the three core annotations of Spring Boot (with code). For more information, please follow other related articles on the PHP Chinese website!

Pythonusesahybridmodelofcompilationandinterpretation:1)ThePythoninterpretercompilessourcecodeintoplatform-independentbytecode.2)ThePythonVirtualMachine(PVM)thenexecutesthisbytecode,balancingeaseofusewithperformance.

Pythonisbothinterpretedandcompiled.1)It'scompiledtobytecodeforportabilityacrossplatforms.2)Thebytecodeistheninterpreted,allowingfordynamictypingandrapiddevelopment,thoughitmaybeslowerthanfullycompiledlanguages.

Forloopsareidealwhenyouknowthenumberofiterationsinadvance,whilewhileloopsarebetterforsituationswhereyouneedtoloopuntilaconditionismet.Forloopsaremoreefficientandreadable,suitableforiteratingoversequences,whereaswhileloopsoffermorecontrolandareusefulf

Forloopsareusedwhenthenumberofiterationsisknowninadvance,whilewhileloopsareusedwhentheiterationsdependonacondition.1)Forloopsareidealforiteratingoversequenceslikelistsorarrays.2)Whileloopsaresuitableforscenarioswheretheloopcontinuesuntilaspecificcond

Pythonisnotpurelyinterpreted;itusesahybridapproachofbytecodecompilationandruntimeinterpretation.1)Pythoncompilessourcecodeintobytecode,whichisthenexecutedbythePythonVirtualMachine(PVM).2)Thisprocessallowsforrapiddevelopmentbutcanimpactperformance,req

ToconcatenatelistsinPythonwiththesameelements,use:1)the operatortokeepduplicates,2)asettoremoveduplicates,or3)listcomprehensionforcontroloverduplicates,eachmethodhasdifferentperformanceandorderimplications.

Pythonisaninterpretedlanguage,offeringeaseofuseandflexibilitybutfacingperformancelimitationsincriticalapplications.1)InterpretedlanguageslikePythonexecuteline-by-line,allowingimmediatefeedbackandrapidprototyping.2)CompiledlanguageslikeC/C transformt

Useforloopswhenthenumberofiterationsisknowninadvance,andwhileloopswheniterationsdependonacondition.1)Forloopsareidealforsequenceslikelistsorranges.2)Whileloopssuitscenarioswheretheloopcontinuesuntilaspecificconditionismet,usefulforuserinputsoralgorit


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

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.

mPDF
mPDF is a PHP library that can generate PDF files from UTF-8 encoded HTML. The original author, Ian Back, wrote mPDF to output PDF files "on the fly" from his website and handle different languages. It is slower than original scripts like HTML2FPDF and produces larger files when using Unicode fonts, but supports CSS styles etc. and has a lot of enhancements. Supports almost all languages, including RTL (Arabic and Hebrew) and CJK (Chinese, Japanese and Korean). Supports nested block-level elements (such as P, DIV),

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

Atom editor mac version download
The most popular open source editor
