[jboss-cvs] JBossCache/src-50/resources ...

Ben Wang bwang at jboss.com
Thu Sep 21 05:48:35 EDT 2006


  User: bwang   
  Date: 06/09/21 05:48:35

  Modified:    src-50/resources  jboss-aop.xml
  Log:
  Re-arranged.
  
  Revision  Changes    Path
  1.3       +90 -94    JBossCache/src-50/resources/jboss-aop.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: jboss-aop.xml
  ===================================================================
  RCS file: /cvsroot/jboss/JBossCache/src-50/resources/jboss-aop.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -b -r1.2 -r1.3
  --- jboss-aop.xml	17 Sep 2006 02:23:38 -0000	1.2
  +++ jboss-aop.xml	21 Sep 2006 09:48:35 -0000	1.3
  @@ -1,101 +1,8 @@
   <?xml version="1.0" encoding="UTF-8"?>
   <aop>
  -   <!-- This is declaration file for JDK50 annotation.
  -        Idea is user will then need only to annotate like:
  -        @org.jboss.cache.aop.annotation.PojoCacheable
  -        in his POJO. There will be no need of jboss-aop.xml from user's side.
  -
  -        For example, see either Address or Person.
  -   -->
  -
  -   <!-- PojoCache 2.0 -->
  -   <!-- If a POJO has PojoCachable annotation, it will be asepctized. -->
  -   <prepare expr="field(* @org.jboss.cache.pojo.annotation.PojoCacheable->*)" />
  -
  -   <!--
  -   Supports inheritance and polymorphism. It can either be a concrete class
  -   or an interface. All sub-classes or interface implementors will be instrumeneted.
  -   -->
  -   <prepare expr="field(* $instanceof{@org.jboss.cache.pojo.annotation.InstanceOfPojoCacheable}->*)" />
  -
  -
  -   <!-- PojoCache 1.4. Is deprecated. Will be removed in 2.1 release -->
  -   <!-- This is declaration file for annotation. We are using JDK1.4 now,
  -        so an annotationc pre-compiler is needed for JBossAop.
  -        See build.xml target annoc for details.
  -        Idea is user will then need only to annotate like:
  -        @@org.jboss.cache.aop.AopMarker
  -        in his POJO. There will be no need of jboss-aop.xml from user's side.
  -        Only extra step is annotation compiling. And in JDK1.5, this step
  -        will not be needed since the implicit annotation support.
  -
  -        For example, see either Address or Person.
  -   -->
  -
  -   <!-- If a POJO has AopMarker annotation, it will be asepctized. -->
  -   <prepare expr="field(* @org.jboss.cache.aop.AopMarker->*)" />
  -
  -   <!--
  -   Supports inheritance and polymorphism. It can either be a concrete class
  -   or an interface. All sub-classes or intrface implementors will be instrumeneted.
  -   -->
  -   <prepare expr="field(* $instanceof{@org.jboss.cache.aop.InstanceOfAopMarker}->*)" />
  -
  -
  -   <!-- This is declaration file for JDK50 annotation.
  -        Idea is user will then need only to annotate like:
  -        @org.jboss.cache.aop.annotation.PojoCacheable
  -        in his POJO. There will be no need of jboss-aop.xml from user's side.
  -
  -        For example, see either Address or Person.
  -   -->
  -
  -   <!-- If a POJO has PojoCachable annotation, it will be asepctized. -->
  -   <prepare expr="field(* @org.jboss.cache.aop.annotation.PojoCacheable->*)" />
   
      <!--
  -   Supports inheritance and polymorphism. It can either be a concrete class
  -   or an interface. All sub-classes or interface implementors will be instrumeneted.
  -   -->
  -   <prepare expr="field(* $instanceof{@org.jboss.cache.aop.annotation.InstanceOfPojoCacheable}->*)" />
  -
  -
  -   <!-- PojoCache 2.0 style -->
  -   <!-- If a POJO has PojoCachable annotation, it will be asepctized. -->
  -   <prepare expr="field(* @org.jboss.cache.pojo.annotation.PojoCacheable->*)" />
  -
  -   <!--
  -   Supports inheritance and polymorphism. It can either be a concrete class
  -   or an interface. All sub-classes or interface implementors will be instrumeneted.
  -   -->
  -   <prepare expr="field(* $instanceof{@org.jboss.cache.pojo.annotation.InstanceOfPojoCacheable}->*)" />
  -
  -   <!-- Observer and Observable to monitor field modification -->
  -   <bind pointcut="
  -      set(* $instanceof{@org.jboss.cache.pojo.annotation.InstanceOfPojoCacheable}->*) OR
  -      set(* @org.jboss.cache.pojo.annotation.PojoCacheable->*)
  -      ">
  -         <interceptor class="org.jboss.cache.pojo.observable.SubjectInterceptor"/>
  -   </bind>
  -
  -   <introduction class="$instanceof{@org.jboss.cache.pojo.annotation.InstanceOfPojoCacheable}">
  -      <mixin>
  -         <interfaces>org.jboss.cache.pojo.observable.Subject</interfaces>
  -         <class>org.jboss.cache.pojo.observable.SubjectImpl</class>
  -         <construction>new org.jboss.cache.pojo.observable.SubjectImpl(this)</construction>
  -      </mixin>
  -   </introduction>
  -
  -   <introduction class="@org.jboss.cache.pojo.annotation.PojoCacheable">
  -      <mixin>
  -         <interfaces>org.jboss.cache.pojo.observable.Subject</interfaces>
  -         <class>org.jboss.cache.pojo.observable.SubjectImpl</class>
  -         <construction>new org.jboss.cache.pojo.observable.SubjectImpl(this)</construction>
  -      </mixin>
  -   </introduction>
  -
  -   <!--
  -   This defines the PojoCache 2.0 interceptor stack.
  +   This defines the PojoCache 2.0 interceptor stack. Unless necessary, don't modify the stack here!
      -->
      <!-- Check id range validity -->
      <interceptor name="CheckId" class="org.jboss.cache.pojo.interceptors.CheckIdInterceptor" scope="PER_INSTANCE"/>
  @@ -147,6 +54,9 @@
         <interceptor-ref name="CheckId"/>
      </stack>
   
  +   <!--
  +   The following section should be READ-ONLY!!
  +   -->
      <!-- This bind the jointpoint to specific in-memory operations. Currently in PojoUtil. -->
      <bind pointcut="execution(*
         @org.jboss.cache.pojo.annotation.Reentrant->toString())">
  @@ -169,4 +79,90 @@
      <bind pointcut="execution(* org.jboss.cache.pojo.impl.PojoCacheImpl->@org.jboss.cache.pojo.annotation.Find(..))">
         <stack-ref name="Find"/>
      </bind>
  +
  +
  +   <!-- This is declaration file for JDK50 annotation.
  +        Idea is user will then need only to annotate like:
  +        @org.jboss.cache.pojo.annotation.PojoCacheable
  +        in his POJO. There will be no need of jboss-aop.xml from user's side.
  +
  +        For example, see either Address or Person.
  +   -->
  +
  +   <!-- PojoCache 2.0 style -->
  +   <!-- If a POJO has PojoCachable annotation, it will be asepctized. -->
  +   <prepare expr="field(* @org.jboss.cache.pojo.annotation.PojoCacheable->*)" />
  +
  +   <!--
  +   Supports inheritance and polymorphism. It can either be a concrete class
  +   or an interface. All sub-classes or interface implementors will be instrumeneted.
  +   -->
  +   <prepare expr="field(* $instanceof{@org.jboss.cache.pojo.annotation.InstanceOfPojoCacheable}->*)" />
  +
  +   <!-- Observer and Observable to monitor field modification -->
  +   <bind pointcut="
  +      set(* $instanceof{@org.jboss.cache.pojo.annotation.InstanceOfPojoCacheable}->*) OR
  +      set(* @org.jboss.cache.pojo.annotation.PojoCacheable->*)
  +      ">
  +         <interceptor class="org.jboss.cache.pojo.observable.SubjectInterceptor"/>
  +   </bind>
  +
  +   <introduction class="$instanceof{@org.jboss.cache.pojo.annotation.InstanceOfPojoCacheable}">
  +      <mixin>
  +         <interfaces>org.jboss.cache.pojo.observable.Subject</interfaces>
  +         <class>org.jboss.cache.pojo.observable.SubjectImpl</class>
  +         <construction>new org.jboss.cache.pojo.observable.SubjectImpl(this)</construction>
  +      </mixin>
  +   </introduction>
  +
  +   <introduction class="@org.jboss.cache.pojo.annotation.PojoCacheable">
  +      <mixin>
  +         <interfaces>org.jboss.cache.pojo.observable.Subject</interfaces>
  +         <class>org.jboss.cache.pojo.observable.SubjectImpl</class>
  +         <construction>new org.jboss.cache.pojo.observable.SubjectImpl(this)</construction>
  +      </mixin>
  +   </introduction>
  +
  +
  +   <!-- PojoCache 1.4. Is deprecated. Will be removed in 2.1 release -->
  +   <!-- This is declaration file for annotation. We are using JDK1.4 now,
  +        so an annotationc pre-compiler is needed for JBossAop.
  +        See build.xml target annoc for details.
  +        Idea is user will then need only to annotate like:
  +        @@org.jboss.cache.aop.AopMarker
  +        in his POJO. There will be no need of jboss-aop.xml from user's side.
  +        Only extra step is annotation compiling. And in JDK1.5, this step
  +        will not be needed since the implicit annotation support.
  +
  +        For example, see either Address or Person.
  +   -->
  +
  +   <!-- If a POJO has AopMarker annotation, it will be asepctized. -->
  +   <prepare expr="field(* @org.jboss.cache.aop.AopMarker->*)" />
  +
  +   <!--
  +   Supports inheritance and polymorphism. It can either be a concrete class
  +   or an interface. All sub-classes or intrface implementors will be instrumeneted.
  +   -->
  +   <prepare expr="field(* $instanceof{@org.jboss.cache.aop.InstanceOfAopMarker}->*)" />
  +
  +
  +   <!-- This is declaration file for JDK50 annotation.
  +        Idea is user will then need only to annotate like:
  +        @org.jboss.cache.aop.annotation.PojoCacheable
  +        in his POJO. There will be no need of jboss-aop.xml from user's side.
  +
  +        For example, see either Address or Person.
  +   -->
  +
  +   <!-- If a POJO has PojoCachable annotation, it will be asepctized. -->
  +   <prepare expr="field(* @org.jboss.cache.aop.annotation.PojoCacheable->*)" />
  +
  +   <!--
  +   Supports inheritance and polymorphism. It can either be a concrete class
  +   or an interface. All sub-classes or interface implementors will be instrumeneted.
  +   -->
  +   <prepare expr="field(* $instanceof{@org.jboss.cache.aop.annotation.InstanceOfPojoCacheable}->*)" />
  +
  +
   </aop>
  
  
  



More information about the jboss-cvs-commits mailing list