Spring/spring-framework
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Polishing

Browse Source
This commit is contained in:
Sam Brannen
2021-04-21 14:15:27 +02:00
parent 80d46ba80e
commit 5740eaf33e
1 changed files with 9 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
src/docs/asciidoc/core/core-beans.adoc
View File

@@ -847,12 +847,12 @@ This approach shows that the factory bean itself can be managed and configured t
dependency injection (DI). See <<beans-factory-properties-detailed,Dependencies and dependency injection (DI). See <<beans-factory-properties-detailed,Dependencies and
Configuration in Detail>>. Configuration in Detail>>.
NOTE: In Spring documentation, "`factory bean`" refers to a bean that is configured in NOTE: In Spring documentation, "factory bean" refers to a bean that is configured in the
the Spring container and that creates objects through an Spring container and that creates objects through an
<<beans-factory-class-instance-factory-method,instance>> or <<beans-factory-class-instance-factory-method,instance>> or
<<beans-factory-class-static-factory-method,static>> factory method. By contrast, <<beans-factory-class-static-factory-method,static>> factory method. By contrast,
`FactoryBean` (notice the capitalization) refers to a Spring-specific `FactoryBean` (notice the capitalization) refers to a Spring-specific
<<beans-factory-extension-factorybean, `FactoryBean` >> implementation class. <<beans-factory-extension-factorybean, `FactoryBean`>> implementation class.
[[beans-factory-type-determination]] [[beans-factory-type-determination]]
@@ -3350,8 +3350,9 @@ of the scope. You can also do the `Scope` registration declaratively, by using t
</beans> </beans>
---- ----
NOTE: When you place `<aop:scoped-proxy/>` in a `FactoryBean` implementation, it is the factory NOTE: When you place `<aop:scoped-proxy/>` within a `<bean>` declaration for a
bean itself that is scoped, not the object returned from `getObject()`. `FactoryBean` implementation, it is the factory bean itself that is scoped, not the object
returned from `getObject()`.
@@ -4545,16 +4546,16 @@ The `FactoryBean<T>` interface provides three methods:
instance can possibly be shared, depending on whether this factory returns singletons instance can possibly be shared, depending on whether this factory returns singletons
or prototypes. or prototypes.
* `boolean isSingleton()`: Returns `true` if this `FactoryBean` returns singletons or * `boolean isSingleton()`: Returns `true` if this `FactoryBean` returns singletons or
`false` otherwise. `false` otherwise. The default implementation of this method returns `true`.
* `Class<?> getObjectType()`: Returns the object type returned by the `getObject()` method * `Class<?> getObjectType()`: Returns the object type returned by the `getObject()` method
or `null` if the type is not known in advance. or `null` if the type is not known in advance.
The `FactoryBean` concept and interface is used in a number of places within the Spring The `FactoryBean` concept and interface are used in a number of places within the Spring
Framework. More than 50 implementations of the `FactoryBean` interface ship with Spring Framework. More than 50 implementations of the `FactoryBean` interface ship with Spring
itself. itself.
When you need to ask a container for an actual `FactoryBean` instance itself instead of When you need to ask a container for an actual `FactoryBean` instance itself instead of
the bean it produces, preface the bean's `id` with the ampersand symbol (`&`) when the bean it produces, prefix the bean's `id` with the ampersand symbol (`&`) when
calling the `getBean()` method of the `ApplicationContext`. So, for a given `FactoryBean` calling the `getBean()` method of the `ApplicationContext`. So, for a given `FactoryBean`
with an `id` of `myBean`, invoking `getBean("myBean")` on the container returns the with an `id` of `myBean`, invoking `getBean("myBean")` on the container returns the
product of the `FactoryBean`, whereas invoking `getBean("&myBean")` returns the product of the `FactoryBean`, whereas invoking `getBean("&myBean")` returns the