In this guide, we will discuss what is Dependency injection (DI) in Spring and what are the different types of Dependency injection (DI).
What is Dependency injection (DI)?
As per official Spring documentation, Dependency injection (DI) is a process whereby objects define their dependencies, that is, the other objects they work with, only through constructor arguments, arguments to a factory method, or properties that are set on the object instance after it is constructed or returned from a factory method. The container then injects those dependencies when it creates the bean. This process is fundamentally the inverse, hence the name Inversion of Control (IoC), of the bean itself controlling the instantiation or location of its dependencies on its own by using direct construction of classes, or the Service Locator pattern.
Advantages of Dependency Injection
- Decoupling: Code is cleaner with the DI principle and decoupling is more effective when objects are provided with their dependencies.
- Easier to test: As such, your classes become easier to test, in particular when the dependencies are on interfaces or abstract base classes, which allow for stub or mock implementations to be used in unit tests.
Types of Dependency Injection
- Constructor-based dependency injection
- Setter-based dependency injection.
What is a Constructor-based dependency injection?
Constructor-based DI is accomplished by the container invoking a constructor with a number of arguments, each representing a dependency.
In the below diagram, the highlighted part shows the Constructor-based dependency injection.
Note that there are multiple implementations for the MessageService interface so to avoid ambiguity, let's use @Qualifier annotation.
In the below diagram, the highlighted part shows the Constructor-based dependency injection.
Let's see the complete example to demonstrate a Constructor-based dependency injection.
As we know, spring java and annotation-based configurations are quite easy to use in spring-based applications so I prefer to use a mix of java and annotation-based spring configurations.
Let's create a spring configuration file using the java class AppConfiguration which is annotated with @Configuration annotation. This is equivalent to a spring XML configuration file without beans definition.
package com.javadevsguide.springframework.di.config;
import org.springframework.context.annotation.ComponentScan;
import org.springframework.context.annotation.Configuration;
@Configuration
@ComponentScan("com.javadevsguide.springframework.di")
public class AppConfiguration {
}
Now create a MessageService interface and provide more than two implementations for it.
public interface MessageService {
public void sendMsg(String message);
}
Let's implement the MessageService interface. There are many ways to send a message like through email, SMS, Twitter, etc.
@Service("EmailService")
public class EmailService implements MessageService{
public void sendMsg(String message) {
System.out.println(message);
}
}
@Service("SMSService")
public class SMSService implements MessageService{
public void sendMsg(String message) {
System.out.println(message);
}
}
@Service("TwitterService")
public class TwitterService implements MessageService{
public void sendMsg(String message) {
System.out.println(message);
}
}
It's time to demonstrate the usage of a Constructor-based dependency injection. To avoid decoupling always use interfaces or abstract base classes as an instance variable and constructor arguments.
In this example, we have used the MessageService interface.
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.beans.factory.annotation.Qualifier;
import org.springframework.stereotype.Component;
import com.javadevsguide.springframework.di.service.MessageService;
@Component
public class ConstructorBasedInjection {
private MessageService messageService;
@Autowired
public ConstructorBasedInjection(@Qualifier("TwitterService")
MessageService messageService) {
super();
this.messageService = messageService;
}
public void processMsg(String message) {
messageService.sendMsg(message);
}
}
It's time to test the usage of a Constructor-based dependency injection.
Let's create an IOC container object that is an ApplicationContext object and get the beans from it.
import org.springframework.context.ApplicationContext; import org.springframework.context.annotation.AnnotationConfigApplicationContext; import com.javadevsguide.springframework.di.config.AppConfiguration; import com.javadevsguide.springframework.di.constructor.ConstructorBasedInjection; public class Application { public static void main(String[] args) { ApplicationContext applicationContext = new AnnotationConfigApplicationContext(AppConfiguration.class); ConstructorBasedInjection constructorBasedInjection = applicationContext.getBean(ConstructorBasedInjection.class); constructorBasedInjection.processMsg("twitter message sending "); } }
Note that we have used Spring Java-based configuration that is AppConfiguration class annotated with @Configuration for configurations.
What is a Setter-based dependency injection?
Setter-based DI is accomplished by the container calling setter methods on your beans after invoking a no-argument constructor or no-argument static factory method to instantiate your bean.
The following example shows a class that can only be dependency-injected using pure setter injection. This class is conventional Java.
Setter-based dependency injection example
It's time to demonstrate the usage of Setter-based dependency injection.
To avoid decoupling always use interfaces or abstract base classes as an instance variable and setter method arguments.
In this example, we have used the MessageService interface.
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.beans.factory.annotation.Qualifier;
import org.springframework.stereotype.Component;
import com.javadevsguide.springframework.di.service.MessageService;
@Component
public class SetterBasedInjection {
private MessageService messageService;
@Autowired
@Qualifier("TwitterService")
public void setMessageService(MessageService messageService) {
this.messageService = messageService;
}
public void processMsg(String message) {
messageService.sendMsg(message);
}
}
It's time to test the usage of a Constructor-based dependency injection. Let's create an IOC container object that is an ApplicationContext object and get the beans from it.
import org.springframework.context.ApplicationContext;
import org.springframework.context.annotation.AnnotationConfigApplicationContext;
import com.javadevsguide.springframework.di.config.AppConfiguration;
import com.javadevsguide.springframework.di.field.FieldBasedInjection;
public class TestApplication {
public static void main(String[] args) {
ApplicationContext applicationContext = new AnnotationConfigApplicationContext(AppConfiguration.class);
SetterBasedInjection setterBasedInjection = applicationContext.getBean(SetterBasedInjection.class);
setterBasedInjection.processMsg("twitter message sending ");
}
}
Note that we have used AppConfiguration class annotated with @Configuration for configurations.
Conclusion
In this example, we have seen the dependency injection in Spring. We have demonstrated constructor-based dependency injection and setter-based dependency injection with examples.
The source code of this article can be found on the GitHub project – this is an Eclipse-based project, so it should be easy to import and run as it is.
GitHub Repository
Github Repository: Guide to Dependency Injection in Spring
Free Spring Boot Tutorial | Full In-depth Course | Learn Spring Boot in 10 Hours
Watch this course on YouTube at Spring Boot Tutorial | Fee 10 Hours Full Course
there is syntax error when you write code , the annotation @Qualifier is disallowed for this location , so you need to put the annotation inside param method like this
ReplyDelete@Autowired
public ConstructorBasedInjection(@Qualifier("EmailService") MessageService messageService) {
super();
this.messageService = messageService;
}