[jboss-cvs] jboss-seam/doc/reference/en/modules ...

[Gavin King]

  User: gavin   
  Date: 06/07/26 18:24:13

  Modified:    doc/reference/en/modules  concepts.xml
  Log:
  interceptor changes
  
  Revision  Changes    Path
  1.31      +19 -8     jboss-seam/doc/reference/en/modules/concepts.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: concepts.xml
  ===================================================================
  RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/concepts.xml,v
  retrieving revision 1.30
  retrieving revision 1.31
  diff -u -b -r1.30 -r1.31
  --- concepts.xml	14 Jul 2006 18:12:23 -0000	1.30
  +++ concepts.xml	26 Jul 2006 22:24:13 -0000	1.31
  @@ -1085,14 +1085,25 @@
   
           <para>
               If interceptor ordering is important (it usually is), you can add 
  -            <literal>@Within</literal> and <literal>@Around</literal> annotations to your
  -            interceptor classes to specify a partial order of interceptors.
  +            <literal>@Interceptor</literal> annotations to your interceptor 
  +            classes to specify a partial order of interceptors.
           </para>
           
  -<programlisting><![CDATA[@Around({BijectionInterceptor.class,
  +<programlisting><![CDATA[@Interceptor(around={BijectionInterceptor.class,
            ValidationInterceptor.class,
  -         ConversationInterceptor.class})
  - at Within(RemoveInterceptor.class)
  +                     ConversationInterceptor.class},
  +             within=RemoveInterceptor.class)
  +public class LoggedInInterceptor
  +{
  +    ...
  +}]]></programlisting>
  +
  +        <para>
  +            You can even have a "client-side" interceptor, that runs around any of the built-in
  +            functionality of EJB3:
  +        </para>
  +
  +<programlisting><![CDATA[@Interceptor(type=CLIENT)
   public class LoggedInInterceptor
   {
       ...