Polish ref docs regarding the BeanFactory API

See gh-28403
This commit is contained in:
Sam Brannen 2022-05-11 17:16:40 +02:00
parent 8098e45bad
commit be782a2197
1 changed files with 12 additions and 12 deletions

View File

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