Book Image

Java 9 Dependency Injection

By : Nilang Patel, Krunal Patel
Book Image

Java 9 Dependency Injection

By: Nilang Patel, Krunal Patel

Overview of this book

Dependency Injection (DI) is a design pattern that allows us to remove the hard-coded dependencies and make our application loosely coupled, extendable, and maintainable. We can implement DI to move the dependency resolution from compile-time to runtime. This book will be your one stop guide to write loosely coupled code using the latest features of Java 9 with frameworks such as Spring 5 and Google Guice. We begin by explaining what DI is and teaching you about IoC containers. Then you’ll learn about object compositions and their role in DI. You’ll find out how to build a modular application and learn how to use DI to focus your efforts on the business logic unique to your application and let the framework handle the infrastructure work to put it all together. Moving on, you’ll gain knowledge of Java 9’s new features and modular framework and how DI works in Java 9. Next, we’ll explore Spring and Guice, the popular frameworks for DI. You’ll see how to define injection keys and configure them at the framework-specific level. After that, you’ll find out about the different types of scopes available in both popular frameworks. You’ll see how to manage dependency of cross-cutting concerns while writing applications through aspect-oriented programming. Towards the end, you’ll learn to integrate any third-party library in your DI-enabled application and explore common pitfalls and recommendations to build a solid application with the help of best practices, patterns, and anti-patterns in DI.
Table of Contents (14 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

DI with Java configuration


So far, we have seen how to define the configuration with XML and annotation. Spring also supports defining configuration completely in Java classes, and there is no more XML required. You need to provide Java classes that take the ownership of creating the beans. In short, it's a source of bean definition.

A class annotated by @Configuration would be considered as Java config for a Spring IoC container. This class should declare methods that actually configure and instantiate the objects of beans that would be managed by containers. All such methods should be annotated with @Bean. Spring will consider all such @Bean annotated methods as a source of bean. Such methods are kinds of factory methods. Let's understand this by looking at the following simple example:

@Configuration
public class JavaBaseSpringConfig {
  @Bean(name="professor")
  public Professor getProfessor() {
    return new Professor();
  }
  @Bean(name="subjectBean")
  public Subject getSubject() ...