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

Clarify BeanPostProcessor ordering rules in ref doc 

Issue: SPR-7550
This commit is contained in:
Chris Beams 2011-06-20 06:48:36 +00:00
parent 95ae6344c5
commit 2d9ced04b1
1 changed files with 27 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
spring-framework-reference/src/beans-extension-points.xml
View File

@ -33,7 +33,10 @@
implementing the <interfacename>Ordered</interfacename> interface too. For implementing the <interfacename>Ordered</interfacename> interface too. For
further details, consult the Javadoc for the further details, consult the Javadoc for the
<interfacename>BeanPostProcessor</interfacename> and <interfacename>BeanPostProcessor</interfacename> and
<interfacename>Ordered</interfacename> interfaces.</para> <interfacename>Ordered</interfacename> interfaces. See also the note below on
<link linkend="beans-factory-programmatically-registering-beanpostprocessors">
programmatic registration of <interfacename>BeanPostProcessors</interfacename>
</link></para>
<note> <note>
<para><literal>BeanPostProcessor</literal>s operate on bean (or object) <para><literal>BeanPostProcessor</literal>s operate on bean (or object)
@ -81,6 +84,29 @@
Bean post-processors can be deployed in the container just like any other Bean post-processors can be deployed in the container just like any other
beans.</para> beans.</para>
<anchor id="beans-factory-programmatically-registering-beanpostprocessors"/>
<note>
<title>Programmatically registering <interfacename>BeanPostProcessors
</interfacename></title>
<para>
While the recommended approach for <interfacename>BeanPostProcessor
</interfacename> registration is through <interfacename>ApplicationContext
</interfacename> auto-detection (as described above), it is also
possible to register them <emphasis>programmatically</emphasis>
against an <interfacename>ApplicationContext</interfacename> using the
<methodname>addBeanPostProcessor</methodname> method. This can be useful
when needing to evaluate conditional logic before registration, or even
for copying bean post processors across contexts in a hierarchy. Note
however that <interfacename>BeanPostProcessors</interfacename> added
programmatically <emphasis>do not respect the <interfacename>Ordered
</interfacename> interface</emphasis>. Here it is the <emphasis>order of
registration</emphasis> that dictates the order of execution. Note also
that <interfacename>BeanPostProcessors</interfacename> registered
programmatically are always processed before those registered through
auto-detection, regardless of any explicit ordering.
</para>
</note>
<note> <note>
<title><interfacename>BeanPostProcessors</interfacename> and AOP <title><interfacename>BeanPostProcessors</interfacename> and AOP
auto-proxying</title> auto-proxying</title>