I. Spring Bean Life Cycle logic execution order (from instantiation to destruction)
(instantiated to destruction)
- Loading bean definition (metadata processing)
-
Spring from the
configuration file (@Configuration), XML file or component scan (@Component)- read bean definition.
- This is metadata processing steps , no instance has been created.
- Related method:
-
BeanDefinitionRegistry#registerBeanDefinition()
- Create the actual bean object through the following ways:
The constructive function is instantiated
- Factory method
-
- Related method:
-
Set the bean name
InstantiationAwareBeanPostProcessor#postProcessBeforeInstantiation()
( )
-
, Spring will call
- Method to
- inform Bean's own name
. This happened before before the injection
BeanNameAware#setBeanName(String name)
.- Use case:
- If bean needs to know its name
BeanNameAware
in the context of the application.setBeanName()
- Set the bean class loader () If bean needs to access its class loader
- If bean needs to know its name
public class MyBean implements BeanNameAware { @Override public void setBeanName(String name) { System.out.println("Bean Name Set: " + name); } }If bean
dynamically load the class
- at runtime.
-
BeanClassLoaderAware#setBeanClassLoader(ClassLoader classLoader)
- Set Beanfactory ( )
- Spring Injects Beanfactory into Bean.
Allow bean
public class MyBean implements BeanClassLoaderAware { @Override public void setBeanClassLoader(ClassLoader classLoader) { System.out.println("ClassLoader Set!"); } }by programming.
-
BeanFactoryAware#setBeanFactory(BeanFactory factory)
- Set the environment
- ()
- If bean needs to access environment variables and attributes , this method will be called. Use case: Used to dynamically access the value in
public class MyBean implements BeanFactoryAware { @Override public void setBeanFactory(BeanFactory beanFactory) { System.out.println("BeanFactory Set!"); } }
-
Set the embedded value parser
)EnvironmentAware#setEnvironment(Environment environment)
(- Allowed bean Analyzing the placement of placement ($ {Property}) .
- Usage: When bean needs manually parsing the placeholder is useful.
public class MyBean implements BeanNameAware { @Override public void setBeanName(String name) { System.out.println("Bean Name Set: " + name); } }
-
Set the resource loader ()
ResourceLoaderAware#setResourceLoader(ResourceLoader loader)
- Only applies to
- ApplicationContext for dynamic loading resources. Use case:
- Loading files, class path resources or external resources.
- Set the application event publisher
- (
)
to publish an eventApplicationEventPublisherAware#setApplicationEventPublisher(ApplicationEventPublisher publisher)
If bean needs- , this method will be called.
- Use case: Used for broadcasting events, such as .
-
ContextRefreshedEvent
(
- )
-
If bean needs Internationalization (I18N) to support
MessageSourceAware#setMessageSource(MessageSource source)
, Spring will inject MessageSource. Set ApplicationContext
)
-
If bean needs to access the entire Spring ApplicationContext , this method will be called.
Example:ApplicationContextAware#setApplicationContext(ApplicationContext ctx)
- Allow dynamic access to
- other beans, environmental settings, etc. .
- Set the servertContext
)
- Only applicable to
- Web applications
, used to access the Web context information .
ServletContextAware#setServletContext(ServletContext ctx)
- The post -processing before the initialization (
Allowed
- before bean
- before the
modified bean.
BeanPostProcessor#postProcessBeforeInitialization()
- Customized initialization
- Custom Method
Custom
-
InitializingBean
afterPropertiesSet()
-
@PostConstruct
After the initialized post -treatment - (
@Bean
)init-method
later -
public class MyBean implements BeanClassLoaderAware { @Override public void setBeanClassLoader(ClassLoader classLoader) { System.out.println("ClassLoader Set!"); } }
Example:
- Used to create proxy, log records or face -oriented programming (AOP)
- .
BeanPostProcessor#postProcessAfterInitialization()
-
bean available - Bean has completely initialized and can be used for applications.
-
2. Destruction stage (bean close the life cycle)
When the application is closed, Spring will be elegant
destroyed bean.
- The treatment before destroyed
- (
)
.DestructionAwareBeanPostProcessor#postProcessBeforeDestruction()
Allows to clean up before the destroy Method -
DisposableBean
If bean is implemented,destroy()
will be called.-
DisposableBean
destroy()
Method (preferred method) -
public class MyBean implements BeanNameAware { @Override public void setBeanName(String name) { System.out.println("Bean Name Set: " + name); } }
- is more modern than , and
call before bean destroyed .
@PreDestroy
-
DisposableBean
Custom (If defined in
-
public class MyBean implements BeanClassLoaderAware { @Override public void setBeanClassLoader(ClassLoader classLoader) { System.out.println("ClassLoader Set!"); } }
- Define the alternative method of cleaning the logic.
-
destroy-method
@Bean
Three, the complete process summary (final order)- ? Bean initialization stage
instantiated bean ()
() (
)- ( )
-
new Bean()
( ) -
setBeanName()
(BeanNameAware
) - (
setBeanClassLoader()
)BeanClassLoaderAware
( - )
setBeanFactory()
BeanFactoryAware
( ) -
setEnvironment()
(EnvironmentAware
) - (
setEmbeddedValueResolver()
)EmbeddedValueResolverAware
( - )
setResourceLoader()
ResourceLoaderAware
/ -
setApplicationEventPublisher()
(ApplicationEventPublisherAware
) -
bean available setMessageSource()
MessageSourceAware
-
setApplicationContext()
? Bean's destruction stageApplicationContextAware
-
setServletContext()
(ServletContextAware
) - (
postProcessBeforeInitialization()
)BeanPostProcessor
-
@PostConstruct
afterPropertiesSet()
-
postProcessAfterInitialization()
More information about interface and methods, please visit:BeanPostProcessor
https://www.php.cn/link/6759d0996526ddc8e27aa550F0B806B1 - I wish you a happy coding! ?
The above is the detailed content of spring-: spring-bean-lifecycle-execution-order. For more information, please follow other related articles on the PHP Chinese website!

Javaispopularforcross-platformdesktopapplicationsduetoits"WriteOnce,RunAnywhere"philosophy.1)ItusesbytecodethatrunsonanyJVM-equippedplatform.2)LibrarieslikeSwingandJavaFXhelpcreatenative-lookingUIs.3)Itsextensivestandardlibrarysupportscompr

Reasons for writing platform-specific code in Java include access to specific operating system features, interacting with specific hardware, and optimizing performance. 1) Use JNA or JNI to access the Windows registry; 2) Interact with Linux-specific hardware drivers through JNI; 3) Use Metal to optimize gaming performance on macOS through JNI. Nevertheless, writing platform-specific code can affect the portability of the code, increase complexity, and potentially pose performance overhead and security risks.

Java will further enhance platform independence through cloud-native applications, multi-platform deployment and cross-language interoperability. 1) Cloud native applications will use GraalVM and Quarkus to increase startup speed. 2) Java will be extended to embedded devices, mobile devices and quantum computers. 3) Through GraalVM, Java will seamlessly integrate with languages such as Python and JavaScript to enhance cross-language interoperability.

Java's strong typed system ensures platform independence through type safety, unified type conversion and polymorphism. 1) Type safety performs type checking at compile time to avoid runtime errors; 2) Unified type conversion rules are consistent across all platforms; 3) Polymorphism and interface mechanisms make the code behave consistently on different platforms.

JNI will destroy Java's platform independence. 1) JNI requires local libraries for a specific platform, 2) local code needs to be compiled and linked on the target platform, 3) Different versions of the operating system or JVM may require different local library versions, 4) local code may introduce security vulnerabilities or cause program crashes.

Emerging technologies pose both threats and enhancements to Java's platform independence. 1) Cloud computing and containerization technologies such as Docker enhance Java's platform independence, but need to be optimized to adapt to different cloud environments. 2) WebAssembly compiles Java code through GraalVM, extending its platform independence, but it needs to compete with other languages for performance.

Different JVM implementations can provide platform independence, but their performance is slightly different. 1. OracleHotSpot and OpenJDKJVM perform similarly in platform independence, but OpenJDK may require additional configuration. 2. IBMJ9JVM performs optimization on specific operating systems. 3. GraalVM supports multiple languages and requires additional configuration. 4. AzulZingJVM requires specific platform adjustments.

Platform independence reduces development costs and shortens development time by running the same set of code on multiple operating systems. Specifically, it is manifested as: 1. Reduce development time, only one set of code is required; 2. Reduce maintenance costs and unify the testing process; 3. Quick iteration and team collaboration to simplify the deployment process.


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

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

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

EditPlus Chinese cracked version
Small size, syntax highlighting, does not support code prompt function

PhpStorm Mac version
The latest (2018.2.1) professional PHP integrated development tool

SublimeText3 Linux new version
SublimeText3 Linux latest version
