From 5e019e1769082599f2923bcbd733a47b34c1e243 Mon Sep 17 00:00:00 2001 From: Stephane Nicoll Date: Fri, 15 Mar 2019 10:51:21 +0100 Subject: [PATCH] Polish "Remove outdated link in documentation" Closes gh-22597 --- src/docs/asciidoc/core/core-beans.adoc | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/src/docs/asciidoc/core/core-beans.adoc b/src/docs/asciidoc/core/core-beans.adoc index fd1c26b4f6c..45409d11612 100644 --- a/src/docs/asciidoc/core/core-beans.adoc +++ b/src/docs/asciidoc/core/core-beans.adoc @@ -10,12 +10,11 @@ This chapter covers Spring's Inversion of Control (IoC) container. == Introduction to the Spring IoC Container and Beans This chapter covers the Spring Framework implementation of the Inversion of Control -(IoC) principle. IoC -is also known as dependency injection (DI). It 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 +(IoC) principle. IoC is also known as dependency injection (DI). It 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) of the bean itself controlling the instantiation or location of its dependencies by using direct construction of classes or a mechanism such as the Service Locator pattern.