At compilation-time the main two factors are number of classes and number of 
pointcut expressions. The number of aspects is not relevant at this point. The 
"complexity" of pointcut expressions is important though, field() and 
constructor execution pointcuts have a higher overhead than method execution 
and construction pointcuts, since field and constructor execution needs to 
instrument all the callers to call the wrappers.

Can the change be made pluggable, so that it runs if a system property is 
present? And if not present, it runs as before?

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3933431#3933431

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3933431


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to