[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [aspectj-users] How AspectJ reflection engine compares against the standard Java one performance wise?
- From: Andy Clement <andrew.clement@xxxxxxxxx>
- Date: Thu, 8 Dec 2011 14:40:31 -0800
- Delivered-to: email@example.com
The AspectJ reflection system is purely for introspecting code, it
isn't for invoking code. The reason it exists is to provide you a
reflection infrastructure that knows about things like ITDs and
pointcuts. If you use standard java reflection against a compiled
aspect you will discover it is a 'class' and that the pointcuts are
represented as 'methods' and that ITDs have manifested special methods
called 'ajc$....' throughout. If you use the AjType reflection system
that will provide you with a more AspectJ oriented view of the types -
it will tell you something is an aspect/pointcut/itd and hide the
And as I say it can't be used to invoke anything, use standard
reflection for that.
On 8 December 2011 12:33, Mark <mark.kharitonov@xxxxxxxxx> wrote:
> In other words, if I am writing plain old Java reflection code, should I
> consider rewriting it using the AspectJ reflection system instead, because
> the latter is faster?
> View this message in context: http://aspectj.2085585.n4.nabble.com/How-AspectJ-reflection-engine-compares-against-the-standard-Java-one-performance-wise-tp4174240p4174240.html
> Sent from the AspectJ - users mailing list archive at Nabble.com.
> aspectj-users mailing list