This detailed walkthrough illustrates the BeanNameAware
interface's setBeanName()
method within a simple Java Spring application. Let's explore the execution flow step-by-step.
1. Program Execution Begins (main())
The program starts in the main()
method. A Spring context is initialized using AnnotationConfigApplicationContext
, loading configuration from TenantConfig.class
. The TenantService
bean is then retrieved.
public static void main(String[] args) { AnnotationConfigApplicationContext context = new AnnotationConfigApplicationContext(TenantConfig.class); TenantService tenantService = context.getBean(TenantService.class); tenantService.processTenantData(); }
2. Spring Context Initialization
AnnotationConfigApplicationContext
processes the @Configuration
-annotated TenantConfig
class. It scans the specified package (adjust basePackages
as needed) for Spring-managed beans (@Service, etc.).
@Configuration @ComponentScan(basePackages = "org.example4") public class TenantConfig { @Bean(name = "tenantA-dataSource") public TenantDataSource tenantADataSource() { return new TenantDataSource(); } @Bean(name = "tenantB-dataSource") public TenantDataSource tenantBDataSource() { return new TenantDataSource(); } }
3. Bean Creation (TenantConfig)
Spring calls the @Bean
methods (tenantADataSource()
and tenantBDataSource()
) to create two TenantDataSource
beans: "tenantA-dataSource" and "tenantB-dataSource".
4. TenantDataSource Initialization
TenantDataSource
implements BeanNameAware
. During bean initialization, Spring calls setBeanName(String beanName)
. This method extracts the tenant name ("tenantA" or "tenantB") from the bean name and sets the database URL accordingly.
public class TenantDataSource implements BeanNameAware { private String tenantName; private String databaseUrl; @Override public void setBeanName(String beanName) { this.tenantName = beanName.split("-")[0]; this.databaseUrl = "jdbc:mysql://localhost:3306/" + tenantName + "_db"; } public void connect() { System.out.println("Connecting to database for tenant: " + tenantName); System.out.println("Database URL: " + databaseUrl); } }
5. TenantService Bean Creation
Spring finds TenantService
(@Service). The constructor uses @Qualifier
to specify which TenantDataSource
beans to inject.
@Service public class TenantService { private final TenantDataSource tenantADataSource; private final TenantDataSource tenantBDataSource; @Autowired public TenantService(@Qualifier("tenantA-dataSource") TenantDataSource tenantA, @Qualifier("tenantB-dataSource") TenantDataSource tenantB) { this.tenantADataSource = tenantA; this.tenantBDataSource = tenantB; } public void processTenantData() { System.out.println("Processing data for all tenants..."); tenantADataSource.connect(); tenantBDataSource.connect(); } }
6. Retrieving TenantService
In main()
, TenantService
is retrieved from the context (context.getBean(TenantService.class)
). It's fully initialized with its dependencies.
7. Calling processTenantData()
tenantService.processTenantData()
is called.
8. Database Connection
tenantADataSource.connect()
and tenantBDataSource.connect()
are called, printing connection details.
9. Program Termination
The program finishes after processing tenant data.
Complete Console Output:
<code>Processing data for all tenants... Connecting to database for tenant: tenantA Database URL: jdbc:mysql://localhost:3306/tenantA_db Connecting to database for tenant: tenantB Database URL: jdbc:mysql://localhost:3306/tenantB_db</code>
For more details on BeanFactory
, refer to the Spring Framework documentation. This example showcases how BeanNameAware
allows beans to be aware of their assigned names within the Spring container, enabling dynamic configuration based on these names.
The above is the detailed content of spring-: setBeanName()-of-BeanNameAware-BeanFactory. 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.
