From 58a9e244e9cab502ae6eb7f6eb2677e148e330fc Mon Sep 17 00:00:00 2001
From: avasseur <avasseur>
Date: Thu, 27 Oct 2005 09:50:55 +0000
Subject: [PATCH] precedence doc for concrete-aspect

---
 docs/devGuideDB/ltw.xml | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/docs/devGuideDB/ltw.xml b/docs/devGuideDB/ltw.xml
index 09ac6520c..45c98d712 100644
--- a/docs/devGuideDB/ltw.xml
+++ b/docs/devGuideDB/ltw.xml
@@ -161,7 +161,9 @@
               <aspect name="com.MyAspect.Inner"/>
 
               <!-- define a concrete aspect inline -->
-              <concrete-aspect name="com.xyz.tracing.MyTracing" extends="tracing.AbstractTracing">
+              <concrete-aspect name="com.xyz.tracing.MyTracing"
+                               extends="tracing.AbstractTracing"
+                               precedence="com.xyz.first, *">
                 <pointcut name="tracingScope" expression="within(org.maw.*)"/>
               </concrete-aspect>
 
@@ -271,7 +273,9 @@
             <title>Using Concrete Aspects</title>
             <para>
                 It is possible to concretize an abstract aspect by the mean of the <literal>META-INF/aop.xml</literal>
-                file. This is usefull to define abstract pointcuts at deployment time.
+                file. This is usefull to define abstract pointcuts at deployment time, and also gives control
+                over precedence through the <literal>precedence</literal> attribute of the
+                <literal>concrete-aspect</literal> XML element.
                 Consider the following:
             </para>
             <programlisting><![CDATA[
-- 
2.39.5