Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Java 9 Dependency Injection
  • Table Of Contents Toc
  • Feedback & Rating feedback
Java 9 Dependency Injection

Java 9 Dependency Injection

By : Nilang Patel , Krunal Patel
4 (3)
close
close
Java 9 Dependency Injection

Java 9 Dependency Injection

4 (3)
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 (8 chapters)
close
close

Choosing AOP frameworks and style of configuration

Once you conclude that you will go ahead with the Aspect programming model to achieve or implement your requirements, this question comes into the picture: should you choose Spring AOP or the full-fledged AspectJ framework ?

After choosing the framework, the question of selecting the style of configuration would come up next. For example, in the case of the AspectJ framework, will you choose AspectJ code style or @AspectJ annotation style? Similarly, in the case of Spring AOP, will you select a Spring XML file or an @AspectJ-based annotation style to define various artifacts such as aspects, point-cuts, advice, and advisors?

Choosing the right framework with the specific style for defining the configuration depends on many factors, such as project requirements, availability of development tools, team expertise, compatibility of...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech

Create a Note

Modal Close icon
You need to login to use this feature.
notes
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Delete Note

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Edit Note

Modal Close icon
Write a note (max 255 characters)
Cancel
Update Note

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY