JBoss.org Community Documentation
This is the original weaving mode. It generates a minimum amount of woven code, only modyfying the target joinpoints. However, the the invocation classes end up calling the target joinpoint using reflection. Hence it will have minimum overhead at weaving time, but incur the extra cost of calling via reflection at runtime.
To use not-optimized classic weaving at compile-time, you need to specify the following
parameters to the aopc
ant task.
optimized
- falsejboss.aop.instrumentor
- org.jboss.aop.instrument.ClassicInstrumentorAn example is shown in the following build.xml snippet. Only the relevant parts are shown.
<aopc optimized="false" compilerclasspathref="..."> <sysproperty key="jboss.aop.instrumentor" \ value="org.jboss.aop.instrument.ClassicInstrumentor"/> ... </aopc>
To turn this weaving mode on when using load-time weaving, you need to specify the same flags as system properties when running your woven application. Here is an example:
java -Djboss.aop.optimized=false \ -Djboss.aop.instrumentor=org.jboss.aop.instrument.ClassicInstrumentor \ [other aop and classpath settings] MyClass