Re: [aspectj-users] How to determine whether a nested class constructor is being called

Okay having had a look at the Java language specification, I have decided this is a bug and am posting it with the following summary. thisJoinPoint.getArgs() exposes incorrect parameter when the join point is a nested class constructor call. Piers Piers wrote: Thanks for the reply Eric. I

Re: [aspectj-users] How to determine whether a nested class constructor is being called

Thanks for the reply Eric. I would agree that the behaviour does not seem to make sense, can anyone confirm our suspicion as to whether this really is a bug? Thank you Piers Eric Bodden wrote: I think that the current behavior does not make much sense. Usually, the additional parameter ho

Re: [aspectj-users] How to determine whether a nested class constructor is being called

I think that the current behavior does not make much sense. Usually, the additional parameter holds the outer instance of the inner class. It should never be null, and I am not sure why null ends up being bound in the aspect in your case. I think that's a bug. Either AspectJ should correctly bind

[aspectj-users] How to determine whether a nested class constructor is being called

Hi I am attempting to write an aspect that checks for null arguments passed to any constructors defined in our project, the problem i am having is that calls to constructors of inner classes get passed a *secret* parameter which evaluates to null. I cannot seem to figure out a way to dete