@@ -33,12 +33,12 @@ is a sub-interface of `BeanFactory`. It adds:
3333* Application-layer specific contexts such as the `WebApplicationContext`
3434for use in web applications.
3535
36- In short, the `BeanFactory` provides the configuration framework and basic
37- functionality, and the `ApplicationContext` adds more enterprise-specific functionality.
38- The `ApplicationContext` is a complete superset of the `BeanFactory` and is used
39- exclusively in this chapter in descriptions of Spring's IoC container. For more
40- information on using the `BeanFactory` instead of the `ApplicationContext,` see
41- <<beans-beanfactory>>.
36+ In short, the `BeanFactory` provides the configuration framework and basic functionality,
37+ and the `ApplicationContext` adds more enterprise-specific functionality. The
38+ `ApplicationContext` is a complete superset of the `BeanFactory` and is used exclusively
39+ in this chapter in descriptions of Spring's IoC container. For more information on using
40+ the `BeanFactory` instead of the `ApplicationContext,` see the section covering the
41+ <<beans-beanfactory, `BeanFactory` API >>.
4242
4343In Spring, the objects that form the backbone of your application and that are managed
4444by the Spring IoC container are called beans. A bean is an object that is
@@ -503,11 +503,11 @@ The following table describes these properties:
503503In addition to bean definitions that contain information on how to create a specific
504504bean, the `ApplicationContext` implementations also permit the registration of existing
505505objects that are created outside the container (by users). This is done by accessing the
506- ApplicationContext's BeanFactory through the `getBeanFactory()` method, which returns the
507- BeanFactory `DefaultListableBeanFactory` implementation. `DefaultListableBeanFactory`
508- supports this registration through the `registerSingleton(..)` and
509- `registerBeanDefinition(..)` methods. However, typical applications work solely with beans
510- defined through regular bean definition metadata.
506+ ApplicationContext's ` BeanFactory` through the `getBeanFactory()` method, which returns
507+ the `DefaultListableBeanFactory` implementation. `DefaultListableBeanFactory` supports
508+ this registration through the `registerSingleton(..)` and `registerBeanDefinition(..)`
509+ methods. However, typical applications work solely with beans defined through regular
510+ bean definition metadata.
511511
512512[NOTE]
513513====
@@ -11155,7 +11155,7 @@ by other application modules on the same machine.
1115511155
1115611156
1115711157[[beans-beanfactory]]
11158- == The `BeanFactory`
11158+ == The `BeanFactory` API
1115911159
1116011160The `BeanFactory` API provides the underlying basis for Spring's IoC functionality.
1116111161Its specific contracts are mostly used in integration with other parts of Spring and
0 commit comments