SPR-5246
+ clarify order of annotation and XML injection git-svn-id: https://src.springframework.org/svn/spring-framework/trunk@2934 50f2f4bb-b051-0410-bef5-90022cba6387
This commit is contained in:
parent
229c393702
commit
b443d3ad7a
|
|
@ -90,7 +90,10 @@ import org.springframework.util.ReflectionUtils;
|
|||
* by the "context:annotation-config" and "context:component-scan" XML tags.
|
||||
* Remove or turn off the default annotation configuration there if you intend
|
||||
* to specify a custom AutowiredAnnotationBeanPostProcessor bean definition.
|
||||
*
|
||||
* <p><b>NOTE:</b> Annotation injection will be performed <i>before</i> XML injection; thus
|
||||
* the latter configuration will override the former for properties wired through
|
||||
* both approaches.
|
||||
*
|
||||
* @author Juergen Hoeller
|
||||
* @author Mark Fisher
|
||||
* @since 2.5
|
||||
|
|
|
|||
|
|
@ -124,6 +124,9 @@ import org.springframework.util.StringUtils;
|
|||
* by the "context:annotation-config" and "context:component-scan" XML tags.
|
||||
* Remove or turn off the default annotation configuration there if you intend
|
||||
* to specify a custom CommonAnnotationBeanPostProcessor bean definition!
|
||||
* <p><b>NOTE:</b> Annotation injection will be performed <i>before</i> XML injection; thus
|
||||
* the latter configuration will override the former for properties wired through
|
||||
* both approaches.
|
||||
*
|
||||
* @author Juergen Hoeller
|
||||
* @since 2.5
|
||||
|
|
|
|||
|
|
@ -4438,7 +4438,14 @@ dataSource.url=jdbc:mysql:mydb</programlisting>
|
|||
<literal>@Qualifier, @Named, and @Provider</literal> if the JSR330 jar is
|
||||
present on the classpath. Use of these annotations also requires that
|
||||
certain <interfacename>BeanPostProcessors</interfacename> be registered
|
||||
within the Spring container. As always, you can register them as
|
||||
within the Spring container.
|
||||
|
||||
<note>Annotation injection is performed <emphasis>before</emphasis> XML injection, thus
|
||||
the latter configuration will override the former for properties wired
|
||||
through both approaches.
|
||||
</note>
|
||||
|
||||
As always, you can register them as
|
||||
individual bean definitions, but they can also be implicitly registered by
|
||||
including the following tag in an XML-based Spring configuration (notice
|
||||
the inclusion of the <literal>context</literal> namespace):</para>
|
||||
|
|
|
|||
Loading…
Reference in New Issue