> Why not? After all creating a new object with reflection resolves in invoking > the null-argument constructor, so why should AspectJ don't trap the > constructor call?
Because the call is performed implicitly, by the reflection API. AJ weaves pieces of advice that apply at call joinpoints into the call side. Now for reflection, how would you want to do that? Obviously you cannot weave into the reflection API because that's implemented in native code. Eric -- Eric Bodden Sable Research Group, McGill University, Montréal, Canada Got an interesting job offer? http://www.bodden.de/hire-me/ _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
