root
/
spring-framework
mirror of https://github.com/spring-projects/spring-framework.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity

Polish 

Closes gh-1089
This commit is contained in:
Stephane Nicoll 2016-07-01 10:58:15 +02:00
parent 66fd86be33
commit cac58738c9
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
src/asciidoc/core-beans.adoc
View File

@ -2680,12 +2680,12 @@ understand the "why" as well as the "how" behind it.
----
To create such a proxy, you insert a child `<aop:scoped-proxy/>` element into a scoped
bean definition. (See <<beans-factory-scopes-other-injection-proxies>> and
<<xsd-configuration>>.) Why do definitions of beans scoped at the `request`, `session`,
`globalSession` and custom-scope levels require the `<aop:scoped-proxy/>` element ?
bean definition (see <<beans-factory-scopes-other-injection-proxies>> and
<<xsd-configuration>>). Why do definitions of beans scoped at the `request`, `session`,
`globalSession` and custom-scope levels require the `<aop:scoped-proxy/>` element?
Let's examine the following singleton bean definition and contrast it with what you need
to define for the aforementioned scopes. (The following `userPreferences` bean
definition as it stands is __incomplete.)__
to define for the aforementioned scopes (note that the following `userPreferences` bean
definition as it stands is __incomplete__).
[source,xml,indent=0]
[subs="verbatim,quotes"]