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

Add note regarding proxyTargetClass for Java config and web controllers 

See gh-23744
This commit is contained in:
Sam Brannen 2019-10-02 13:11:06 +02:00
parent 96930924b2
commit f16e29892e
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/docs/asciidoc/web/webmvc.adoc
View File

@ -1440,8 +1440,10 @@ controller. When this is the case, for controllers specifically, we recommend
using class-based proxying. This is typically the default choice with controllers. using class-based proxying. This is typically the default choice with controllers.
However, if a controller must implement an interface that is not a Spring Context However, if a controller must implement an interface that is not a Spring Context
callback (such as `InitializingBean`, `*Aware`, and others), you may need to explicitly callback (such as `InitializingBean`, `*Aware`, and others), you may need to explicitly
configure class-based proxying. For example, with `<tx:annotation-driven/>`, you can configure class-based proxying. For example, with `<tx:annotation-driven/>` you can
change to `<tx:annotation-driven proxy-target-class="true"/>`. change to `<tx:annotation-driven proxy-target-class="true"/>`, and with
`@EnableTransactionManagement` you can change to
`@EnableTransactionManagement(proxyTargetClass = true)`.