Bushan,
This is a good topic as I would think
Caching can be treated as an
Aspect.
Recently I have been reading about AOP and some people suggesting it to be an approach for studying performance of an application.
When you say "studying performance"; I presume you mean the profilling of an application. Just like logging; profilling is a great application for AOP.
BTW
JSR138 is about
Performance Metric Instrumentation.
Dosen't weaving of aspects itself affect the performance ?
One class of AOP frameworks uses byte-code manipulation to inject code to intercept your method calls or class loading. I don't have numbers but since the aspects are being weaved in at the bytecode instruction set level; I would assume it is minimal (but only if the bytecode is efficiently coded, of course).
Finally, have you followed Cedric Beust's AOP Caching challenge. Here's the
link Cheers,
Gavin