From 3d3f8f3219d9e6e0af0bbea5260ebdf70035efe2 Mon Sep 17 00:00:00 2001
From: Juergen Hoeller <jhoeller@vmware.com>
Date: Fri, 11 Jun 2010 13:28:14 +0000
Subject: [PATCH] added explicit section on autodetecting aspects through
 component scanning (SPR-7246)

---
 spring-framework-reference/src/aop.xml | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/spring-framework-reference/src/aop.xml b/spring-framework-reference/src/aop.xml
index 76ccf963e6..62bf969ee4 100644
--- a/spring-framework-reference/src/aop.xml
+++ b/spring-framework-reference/src/aop.xml
@@ -391,7 +391,20 @@ public class NotVeryUsefulAspect {
       introduction (inter-type) declarations.</para>
 
       <note>
-        <title>Advising aspects</title>
+        <title>Autodetecting aspects through component scanning</title>
+
+        <para>You may register aspect classes as regular beans in your Spring
+        XML configuration, or autodetect them throuch classpath scanning -
+        just like any other Spring-managed bean. However, note that the
+        <emphasis>@Aspect</emphasis> annotation is <emphasis>not</emphasis>
+        sufficient for autodetection in the classpath: For that purpose,
+        you need to add a separate <emphasis>@Component</emphasis> annotation
+        (or alternatively a custom stereotype annotation that qualifies,
+        as per the rules of Spring's component scanner).</para>
+      </note>
+
+      <note>
+        <title>Advising aspects with other aspects?</title>
 
         <para>In Spring AOP, it is <emphasis>not</emphasis> possible to have
         aspects themselves be the target of advice from other aspects. The