List of Figures

 

Chapter 1. Dependency injection: what’s all the hype?

Figure 1.1. Email is composed locally, delivered across an internet relay, and received by an inbox.

Figure 1.2. Object Emailer is composed of another object, SpellChecker.

Figure 1.3. An email service that checks spelling in English

Figure 1.4. An email service that checks spelling using an abstract spelling service

Figure 1.5. The same Emailer class can now check spelling in a variety of languages.

Figure 1.6. A client requests its dependencies from a Factory.

Figure 1.7. EmailerFactory constructs and assembles a Japanese Emailer with various dependencies.

Figure 1.8. Service locators find specific services requested by clients.

Figure 1.9. The injector provides an object with its dependencies.

Figure 1.10. The injector constructs and wires SimpleEmailClient with a dependency (Emailer).

Figure 1.11. Client code that uses an email service provided by dependency injection

Chapter 2. Time for injection

Figure 2.1. Injector is bootstrapped in the init lifecycle stage of a web application, on deployment.

Figure 2.2. Injector is bootstrapped during a desktop application’s startup.

Figure 2.3. Injector is bootstrapped every time it is needed (on demand).

Figure 2.4. Injector is bootstrapped on first use (lazily).

Figure 2.5. A class model of the emailer and English spellchecker

Figure 2.6. Injector obtains emailer for a client, which is then used to send mail.

Figure 2.7. An injector can be configured in several different ways.