The code to build the JoinPoint static part objects is generated at compile/weave time. Basically the static initializer in your class becomes a big long list of joinpoint create calls. Adding annotations to the mix would just mean that the reflective calls to fetch them for inclusion in the joinpoint object would be made in your static initializers (or possibly lazily when requested), since, as I say, you can't new up annotations in an easy way. Effectively we would just be moving the reflective calls around, they'd still be made.
Andy On 14 December 2011 13:41, Mark <[email protected]> wrote: > So, basically it is only available through the reflection on the respective > type/method/field? But, since they are indeed available during the > compilation, you could have cached them in thisJoinPointStaticPart? > > I would really like this feature, so here you go - > https://bugs.eclipse.org/bugs/show_bug.cgi?id=366757 > > Thanks. > > -- > View this message in context: > http://aspectj.2085585.n4.nabble.com/Why-annotations-are-not-exposed-through-JoinPoint-StaticPart-tp4196637p4197179.html > Sent from the AspectJ - users mailing list archive at Nabble.com. > _______________________________________________ > aspectj-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/aspectj-users _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
