The @Qualifier annotation in Spring Boot is used to resolve ambiguity when you have multiple beans of the same type but want to inject a specific one. It helps Spring determine which bean should be autowired when multiple candidates exist.
Here are all the common scenarios where @Qualifier is useful with examples:
Scenario 1: Multiple Beans of the Same Type
You may have multiple beans of the same type, and you want to inject a specific one.
Example:
import org.springframework.stereotype.Component; @Component public class Dog implements Animal { @Override public String sound() { return "Bark"; } } @Component public class Cat implements Animal { @Override public String sound() { return "Meow"; } }
Here, both Dog and Cat implement the Animal interface.
Usage of @Qualifier:
import org.springframework.beans.factory.annotation.Autowired; import org.springframework.beans.factory.annotation.Qualifier; import org.springframework.stereotype.Service; @Service public class AnimalService { private final Animal animal; @Autowired public AnimalService(@Qualifier("cat") Animal animal) { this.animal = animal; } public String getAnimalSound() { return animal.sound(); } }
In this example, the @Qualifier("cat") annotation specifies that the Cat bean should be injected into the AnimalService. Without @Qualifier, Spring would throw an exception due to ambiguity.
Scenario 2: Using @Qualifier with Primary and Secondary Beans
Sometimes, you may have one "primary" bean and others that are less frequently used, but you still want to be able to inject the specific ones with @Qualifier.
Example:
@Component @Primary public class Dog implements Animal { @Override public String sound() { return "Bark"; } } @Component public class Cat implements Animal { @Override public String sound() { return "Meow"; } }
The @primary annotation ensures that Dog is injected by default. But you can still use @Qualifier to inject Cat.
Usage of @Qualifier to Override @primary:
@Service public class AnimalService { private final Animal animal; @Autowired public AnimalService(@Qualifier("cat") Animal animal) { this.animal = animal; } public String getAnimalSound() { return animal.sound(); } }
In this case, despite Dog being marked as @primary, the Cat bean is injected due to the @Qualifier annotation.
Scenario 3: @Qualifier with Constructor Injection and Field Injection
@Qualifier can be used with both constructor-based and field-based injection.
Example: Field Injection with @Qualifier:
@Service public class AnimalService { @Autowired @Qualifier("dog") private Animal animal; public String getAnimalSound() { return animal.sound(); } }
In this case, the @Qualifier("dog") ensures that the Dog bean is injected into the AnimalService.
Scenario 4: @Qualifier with Method Parameter Injection
You can also use @Qualifier when injecting dependencies via method parameters.
Example:
@Service public class AnimalService { private Animal animal; @Autowired public void setAnimal(@Qualifier("dog") Animal animal) { this.animal = animal; } public String getAnimalSound() { return animal.sound(); } }
Here, @Qualifier("dog") ensures that the Dog bean is injected through the setter method.
Scenario 5: @Qualifier with Custom Annotations
You can create custom qualifiers to avoid hardcoding bean names, making the code cleaner and more maintainable.
Example: Custom Qualifier:
Create a Custom Qualifier:
import org.springframework.beans.factory.annotation.Qualifier; import java.lang.annotation.Retention; import java.lang.annotation.RetentionPolicy; @Qualifier @Retention(RetentionPolicy.RUNTIME) public @interface DogQualifier { }
Apply the Custom Qualifier:
@Component @DogQualifier public class Dog implements Animal { @Override public String sound() { return "Bark"; } } @Component public class Cat implements Animal { @Override public String sound() { return "Meow"; } }
Inject Using the Custom Qualifier:
@Service public class AnimalService { private final Animal animal; @Autowired public AnimalService(@DogQualifier Animal animal) { this.animal = animal; } public String getAnimalSound() { return animal.sound(); } }
In this example, @DogQualifier is used to specify which bean to inject, instead of using @Qualifier("dog").
Scenario 6: @Qualifier in Collections
You can use @Qualifier when autowiring a collection of beans to ensure that only specific beans are injected.
Example:
import org.springframework.beans.factory.annotation.Qualifier; import org.springframework.stereotype.Component; @Component @Qualifier("domestic") public class Dog implements Animal { @Override public String sound() { return "Bark"; } } @Component @Qualifier("domestic") public class Cat implements Animal { @Override public String sound() { return "Meow"; } } @Component public class Lion implements Animal { @Override public String sound() { return "Roar"; } }
Usage with a Collection:
@Service public class AnimalService { private final List<animal> animals; @Autowired public AnimalService(@Qualifier("domestic") List<animal> animals) { this.animals = animals; } public void printAnimalSounds() { animals.forEach(animal -> System.out.println(animal.sound())); } } </animal></animal>
In this example, only Dog and Cat beans are injected because they are marked with the @Qualifier("domestic").
Summary:
@Qualifier helps in injecting specific beans when there are multiple candidates of the same type.
It is used in scenarios like constructor injection, field injection, method injection, custom qualifiers, and even with collections.
By understanding these scenarios, you can use @Qualifier effectively to resolve ambiguity and manage bean injection in a Spring Boot application.
The above is the detailed content of @Qualifier Annotation Spring Boot Explained. For more information, please follow other related articles on the PHP Chinese website!

Bytecodeachievesplatformindependencebybeingexecutedbyavirtualmachine(VM),allowingcodetorunonanyplatformwiththeappropriateVM.Forexample,JavabytecodecanrunonanydevicewithaJVM,enabling"writeonce,runanywhere"functionality.Whilebytecodeoffersenh

Java cannot achieve 100% platform independence, but its platform independence is implemented through JVM and bytecode to ensure that the code runs on different platforms. Specific implementations include: 1. Compilation into bytecode; 2. Interpretation and execution of JVM; 3. Consistency of the standard library. However, JVM implementation differences, operating system and hardware differences, and compatibility of third-party libraries may affect its platform independence.

Java realizes platform independence through "write once, run everywhere" and improves code maintainability: 1. High code reuse and reduces duplicate development; 2. Low maintenance cost, only one modification is required; 3. High team collaboration efficiency is high, convenient for knowledge sharing.

The main challenges facing creating a JVM on a new platform include hardware compatibility, operating system compatibility, and performance optimization. 1. Hardware compatibility: It is necessary to ensure that the JVM can correctly use the processor instruction set of the new platform, such as RISC-V. 2. Operating system compatibility: The JVM needs to correctly call the system API of the new platform, such as Linux. 3. Performance optimization: Performance testing and tuning are required, and the garbage collection strategy is adjusted to adapt to the memory characteristics of the new platform.

JavaFXeffectivelyaddressesplatforminconsistenciesinGUIdevelopmentbyusingaplatform-agnosticscenegraphandCSSstyling.1)Itabstractsplatformspecificsthroughascenegraph,ensuringconsistentrenderingacrossWindows,macOS,andLinux.2)CSSstylingallowsforfine-tunin

JVM works by converting Java code into machine code and managing resources. 1) Class loading: Load the .class file into memory. 2) Runtime data area: manage memory area. 3) Execution engine: interpret or compile execution bytecode. 4) Local method interface: interact with the operating system through JNI.

JVM enables Java to run across platforms. 1) JVM loads, validates and executes bytecode. 2) JVM's work includes class loading, bytecode verification, interpretation execution and memory management. 3) JVM supports advanced features such as dynamic class loading and reflection.

Java applications can run on different operating systems through the following steps: 1) Use File or Paths class to process file paths; 2) Set and obtain environment variables through System.getenv(); 3) Use Maven or Gradle to manage dependencies and test. Java's cross-platform capabilities rely on the JVM's abstraction layer, but still require manual handling of certain operating system-specific features.


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

Atom editor mac version download
The most popular open source editor

VSCode Windows 64-bit Download
A free and powerful IDE editor launched by Microsoft

Zend Studio 13.0.1
Powerful PHP integrated development environment

SublimeText3 English version
Recommended: Win version, supports code prompts!

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