Social Media

Dependency Injection (DI)

Dependency Injection(DI) is part of larger concept of Inversion of Control(IoC). It means the object is not responsible for creating its own dependencies, and dependencies will be injected when it needs to know them

Em, What?

Consider the following Cyclist class. It creates and manages its own dependencies in its constructor –

[sourcecode lang=”java”] public class Cyclist
private RacingBike racingBike;

public Cyclist()
// Establish own dependency
racingBike = new RacingBike();

In dependency injection using Spring this class would be rewritten as –

[sourcecode lang=”java”] public class Cyclist {
private Bike bike;

public void setBike(Bike bike){ = bike;

public void getBike(){
return bike;

Client code –

[sourcecode lang=”java”] public class App {
public static void main(String[] args) {
ApplicationContext context = new ClassPathXmlApplicationContext("beans.xml");
Cyclist cyclist = (Cyclist) context.getBean("cyclist");

The DI framework would then “inject” the bike dependency through a config file –

[sourcecode lang=”xml”] <?xml version="1.0" encoding="UTF-8"?>

<beans xmlns=""

<bean id="racingBike" class="RacingBike">
<bean id="cyclist" class="Cyclist">
<property name="bike" value="racingBike"/>


The advantages of DI are –

  • Testable – Main advantage, and this helps improve code quality
  • Loose coupling – Code to interfaces
  • Reuseable – Can replace implementation classes, so you could swap JDBC for say hibernate
  • Single responsibilty principle – Classes can focus on their own tasks

Types of injection –

  • Constructor
  • Setter
  • Interface – not in Spring

About the Author Martin Farrell

My name is Martin Farrell. I have almost 20 years Java experience. I specialize inthe Spring Framework and JEE. I’ve consulted to a range of businesses, and have provide Java and Spring mentoring and training. You can learn more at About or on my consultancy website Glendevon Software

follow me on:

Leave a Comment: