Hi, I've read about performance issues on accessing the join point context (i.e. thisJoinPoint.getArgs()). I'm writing a logging facade and sometimes it's necessary to access the argument list or executing context (getThis). Using of the join point context depends if the log level is appropriate. So in production the debugging information won't be used, so accessing the arguments or getThis() is wasting time and memory.
So my question is: Using the thisJoinPoint instance already has an impact on the performance (speed or memory usage) even the thisJoinPoint getters won't be called? Does the code weaver add reflecting code fragments to the advice, even the join point is not used? Thx Marko -- View this message in context: http://aspectj.2085585.n4.nabble.com/Is-there-any-performance-issue-using-thisJoinPoint-tp3160915p3160915.html Sent from the AspectJ - users mailing list archive at Nabble.com. _______________________________________________ aspectj-users mailing list aspectj-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users
