AOP 2.0 uses a different weaving model "Generated Advisor". You can select the
old one by passing in the old instrumentor into aopc, which at least should fix the memory
leaks.
| <aopc optimized="${optimized}"
compilerclasspathref="aop.task.classpath">
| ....
| <sysproperty key="jboss.aop.instrumentor"
value="org.jboss.aop.instrument.ClassicInstrumentor"/>
| ....
| </aopc>
|
However, as I mentioned elsewhere compatibilty of woven classes across releases completely
slipped my mind until the cache guys mentioned it so YMMV. I'll take a look though
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031147#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...