From e50bf403b26657b4b39a6be0e34b7170dbc788a9 Mon Sep 17 00:00:00 2001
From: acolyer <acolyer>
Date: Tue, 13 Dec 2005 22:17:13 +0000
Subject: [PATCH] fix section on annotation inheritance matching

---
 docs/adk15ProgGuideDB/annotations.xml | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/docs/adk15ProgGuideDB/annotations.xml b/docs/adk15ProgGuideDB/annotations.xml
index a49da8ddd..f0eb7de7d 100644
--- a/docs/adk15ProgGuideDB/annotations.xml
+++ b/docs/adk15ProgGuideDB/annotations.xml
@@ -1180,12 +1180,11 @@
   	</para>
   	
   	<para>
-  	    The pointcut <literal>c1MethodCall</literal> matches both 
-  	    <literal>c1.aMethod()</literal> and <literal>c2.aMethod()</literal>. The call
-  	    to <literal>c2.aMethod</literal> is matched because the call join point has
-  	    multiple signatures (<literal>@SomeAnnotation C1.aMethod()</literal> and
-  	    <literal>C2.aMethod()</literal>), and the former of those signatures is
-  	    exactly matched by the pattern.
+  	    The pointcut <literal>annotatedMethodCall</literal> matches  
+  	    <literal>c1.aMethod()</literal> but not <literal>c2.aMethod()</literal>. The call
+  	    to <literal>c2.aMethod</literal> is not matched because join point matching for
+  	    modifiers (the visibility modifiers, annotations, and throws clause) is based on
+  	    the subject of the join point (the method actually being called).
   	</para>
   	
   </sect2>
-- 
2.39.5