From: Bill B. <pat...@us...> - 2004-05-28 23:46:49
|
User: patriot1burke Date: 04/05/28 16:46:40 Modified: docs/examples/caller caller.wiki Log: expanded Invocation interface for metadata resolved by Class (i.e. annotations) This was for EJB 3 code Revision Changes Path 1.3 +1 -1 jboss-aop/docs/examples/caller/caller.wiki Index: caller.wiki =================================================================== RCS file: /cvsroot/jboss/jboss-aop/docs/examples/caller/caller.wiki,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- caller.wiki 28 Apr 2004 04:58:56 -0000 1.2 +++ caller.wiki 28 May 2004 23:46:39 -0000 1.3 @@ -3,7 +3,7 @@ !Callers Execution pointcuts on methods and constructors are very useful, but limiting some times. For instance, what if you don't want a method to be intercepted once you are within the method's class? Another problem is that JBoss AOP does not allow you to have an execution pointcut applied to any Java system classes. This is where caller pointcuts come in. Executions are invoked whenever the method is called within the method itself. Callers are invoked at the point of the calling code. Callers allow you to specify what method in what class calls whatever method. Confused? Here's some examples from jboss-aop.xml. {{{ - <bind pointcut="call(int java.util.ArrayList->size() AND withincode(void Driver->caller())"> + <bind pointcut="call(int java.util.ArrayList->size()) AND withincode(void Driver->caller()"> <interceptor class="CallerInterceptor1"/> </bind> }}} |