Set Loadtime Weaving with System.out Logging
Loadtime weaving with Syetem.out logging For this example we pass in ... ... when running the application, so logging is now turned on. In this case neither jboss-logging-log4j.jar nor log4j.jar are on the classpath, so JBoss AOP will default to use the System.out logging mechanism. To run the example with System.out logging, you should run: $ ant run.loadtime.system.out.logging This will generate quite a lot of output during the 'run' stage, the most important of which are outlined here: run.loadtime.system.out.logging: ... [java] [aop-debug] org.jboss.aop.instrument.Instrumentor trying to transform POJO [java] [aop-debug] org.jboss.aop.instrument.CallerTransformer There are no caller pointcuts! [java] [aop-debug] org.jboss.aop.instrument.JoinpointSimpleClassifier javassist.CtMethod@ae60ead5[public notwoven ()V] matches no pointcuts [java] [aop-debug] org.jboss.aop.instrument.JoinpointSimpleClassifier javassist.CtMethod@7c6e6140[public boundMethod ()V] matches pointcut: execution(public void POJO->boundMethod()) [java] [aop-debug] org.jboss.aop.instrument.JoinpointSimpleClassifier javassist.CtConstructor@64c34e[public POJO ()V] matches no pointcuts [java] [aop-debug] org.jboss.aop.instrument.Instrumentor was POJO converted: true ... [java] --- pojo.notwoven(); --- [java] notwoven() [java] --- pojo.boundMethod(); --- ... [java] <<< Entering SimpleInterceptor [java] boundMethod [java] >>> Leaving SimpleInterceptor We can see that the weaver attempts to transform POJO, and finds that POJO.boundMethod() matches the single pointcut we have in out jboss-aop.xml: execution(public void POJO->boundMethod(). The other methods in POJO do not match this pointcut.