method is called. This will happen automatically if Bean implement the interface. setBeanName(String beanName)
BeanNameAware
The following is a detailed explanation of when when, who and how to call:
setBeanName()
Who calls ?
Spring IOC (control reversal) container
call setBeanName()
.
When Bean is initialized and registered to the Spring context, the Spring container checks whether Bean has implemented the interface. If it is implemented, Spring will automatically call the method and transmit the setBeanName()
Bean name
Bean name BeanNameAware
. setBeanName()
When is it called?
setBeanName()
Bean initialization stage
: - After
Bean instantiated, But In any other initialized callback
(such asor
The surrounding life cycle events are shown below:setBeanName()
) before call.@PostConstruct
InitializingBean.afterPropertiesSet()
The order of the event : -
Spring container instantiated bean. Spring determines the name of the bean from the configuration (such as
or).
If bean is implemented, thesetBeanName()
- method is called, and the name of the bean is passed as a parameter.
- Relying on injection and other initialization operations.
-
@Bean
@Component
-
BeanNameAware
How to call SpringsetBeanName()
?
Bean's registration period :
Spring register all bean to the
application context setBeanName()
. When registering Bean, it associates its name with Bean (explicitly defined or automatically generated).
-
Check :
During the initialization period, Spring will check whether bean has achieved . If so, Spring will automatically call the method.
-
Pass the name of the bean :
BeanNameAware
The name of the bean passed to is:BeanNameAware
The name specified in the configuration (setBeanName()
or - The default name generated by Spring (e.g., class name, first letter sketch:
corresponding ).
setBeanName()
- Simplified code process
-
@Bean(name = "myBean")
The following is the way Spring calls@Component("myBean")
in the Bean's life cycle:
// Spring容器初始化(偽代碼) public class BeanFactory { public Object createBean(Class<?> beanClass, String beanName) { // 步驟1:實(shí)例化bean Object bean = instantiateBean(beanClass); // 步驟2:檢查bean是否實(shí)現(xiàn)了BeanNameAware if (bean instanceof BeanNameAware) { // 步驟3:調(diào)用setBeanName()并傳遞bean的名稱 ((BeanNameAware) bean).setBeanName(beanName); } // 步驟4:繼續(xù)進(jìn)行依賴注入和其他生命周期回調(diào) injectDependencies(bean); initializeBean(bean); return bean; } }
Practice example
bean definition
@Configuration public class AppConfig { @Bean(name = "tenantA-dataSource") public TenantDataSource tenantADataSource() { return new TenantDataSource(); } }
bean implementation
import org.springframework.beans.factory.BeanNameAware; public class TenantDataSource implements BeanNameAware { private String tenantName; private String databaseUrl; @Override public void setBeanName(String beanName) { // 從bean名稱中提取租戶名稱 if (beanName.contains("-")) { this.tenantName = beanName.split("-")[0]; } else { throw new IllegalArgumentException("無效的bean命名約定。預(yù)期格式:<tenantname>-dataSource"); } // 根據(jù)租戶名稱動(dòng)態(tài)分配數(shù)據(jù)庫(kù)URL this.databaseUrl = "jdbc:mysql://localhost:3306/" + tenantName + "_db"; System.out.println("setBeanName() called for: " + beanName + ", resolved tenant: " + tenantName); } public void connect() { System.out.println("Connecting to database: " + databaseUrl); } }
Main application <主>
import org.springframework.context.ApplicationContext; import org.springframework.context.annotation.AnnotationConfigApplicationContext; public class Main { public static void main(String[] args) { // 初始化Spring上下文 ApplicationContext context = new AnnotationConfigApplicationContext(AppConfig.class); // 獲取bean TenantDataSource tenantA = (TenantDataSource) context.getBean("tenantA-dataSource"); // 使用bean tenantA.connect(); } }
Output <輸><code>setBeanName() called for: tenantA-dataSource, resolved tenant: tenantA Connecting to database: jdbc:mysql://localhost:3306/tenantA_db</code>
Use case
setBeanName()
- :
-
Use the name of the bean to associate (such as the attributes specific to the tenants).
Debug
: - Add debugging or log records according to the name of the bean.
:
Dynamically modify Bean behavior according to the Bean name. -
or external configuration.setBeanName()
Avoid the logic too complicated by hard -coding Bean name dependencies. For this kind of situation, it is best to use an external configuration source or dynamic routing. -
The above is the detailed content of spring-: who-calls-setBeanName()?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

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

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

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

Hot Topics

The difference between HashMap and Hashtable is mainly reflected in thread safety, null value support and performance. 1. In terms of thread safety, Hashtable is thread-safe, and its methods are mostly synchronous methods, while HashMap does not perform synchronization processing, which is not thread-safe; 2. In terms of null value support, HashMap allows one null key and multiple null values, while Hashtable does not allow null keys or values, otherwise a NullPointerException will be thrown; 3. In terms of performance, HashMap is more efficient because there is no synchronization mechanism, and Hashtable has a low locking performance for each operation. It is recommended to use ConcurrentHashMap instead.

Java uses wrapper classes because basic data types cannot directly participate in object-oriented operations, and object forms are often required in actual needs; 1. Collection classes can only store objects, such as Lists use automatic boxing to store numerical values; 2. Generics do not support basic types, and packaging classes must be used as type parameters; 3. Packaging classes can represent null values ??to distinguish unset or missing data; 4. Packaging classes provide practical methods such as string conversion to facilitate data parsing and processing, so in scenarios where these characteristics are needed, packaging classes are indispensable.

StaticmethodsininterfaceswereintroducedinJava8toallowutilityfunctionswithintheinterfaceitself.BeforeJava8,suchfunctionsrequiredseparatehelperclasses,leadingtodisorganizedcode.Now,staticmethodsprovidethreekeybenefits:1)theyenableutilitymethodsdirectly

The JIT compiler optimizes code through four methods: method inline, hot spot detection and compilation, type speculation and devirtualization, and redundant operation elimination. 1. Method inline reduces call overhead and inserts frequently called small methods directly into the call; 2. Hot spot detection and high-frequency code execution and centrally optimize it to save resources; 3. Type speculation collects runtime type information to achieve devirtualization calls, improving efficiency; 4. Redundant operations eliminate useless calculations and inspections based on operational data deletion, enhancing performance.

Instance initialization blocks are used in Java to run initialization logic when creating objects, which are executed before the constructor. It is suitable for scenarios where multiple constructors share initialization code, complex field initialization, or anonymous class initialization scenarios. Unlike static initialization blocks, it is executed every time it is instantiated, while static initialization blocks only run once when the class is loaded.

InJava,thefinalkeywordpreventsavariable’svaluefrombeingchangedafterassignment,butitsbehaviordiffersforprimitivesandobjectreferences.Forprimitivevariables,finalmakesthevalueconstant,asinfinalintMAX_SPEED=100;wherereassignmentcausesanerror.Forobjectref

Factory mode is used to encapsulate object creation logic, making the code more flexible, easy to maintain, and loosely coupled. The core answer is: by centrally managing object creation logic, hiding implementation details, and supporting the creation of multiple related objects. The specific description is as follows: the factory mode handes object creation to a special factory class or method for processing, avoiding the use of newClass() directly; it is suitable for scenarios where multiple types of related objects are created, creation logic may change, and implementation details need to be hidden; for example, in the payment processor, Stripe, PayPal and other instances are created through factories; its implementation includes the object returned by the factory class based on input parameters, and all objects realize a common interface; common variants include simple factories, factory methods and abstract factories, which are suitable for different complexities.

There are two types of conversion: implicit and explicit. 1. Implicit conversion occurs automatically, such as converting int to double; 2. Explicit conversion requires manual operation, such as using (int)myDouble. A case where type conversion is required includes processing user input, mathematical operations, or passing different types of values ??between functions. Issues that need to be noted are: turning floating-point numbers into integers will truncate the fractional part, turning large types into small types may lead to data loss, and some languages ??do not allow direct conversion of specific types. A proper understanding of language conversion rules helps avoid errors.
