Well, a tool won't tell you what is wrong with the code, since it doesn't
know what you intend to express. If you can show example code of what you
intend to advise, perhaps someone can help you (it is really difficult to
know what you want from the email).
For you earlier question, the fact that you are using IntelliJ may be a part
of the problem. Its support, while has improved a lot recently, in nowhere
as good as that in Eclipse. So you may want to give Eclipse+AJDT a try.
-Ramnivas
On Tue, Jul 13, 2010 at 9:58 PM, Stephen Boesch <java...@gmail.com> wrote:
> So here's an example: I have code below that does not work. How can I
> found out what's wrong with it?
> The intention is to advise all get*() methods in the dao class. Well
> that part works alone, but when adding in the "notInMethods" pointcut, then
> nothing works. So what tooling can tell me why nothing gets advised
> anymore?
>
> @Pointcut(value = "execution(public * *.getManagedClass())")
> public void notInMethods() {
> }
>
> @Around(value = "!notInMethods() && execution(public * *.get* (..)) &&
> this(dao)", argNames = "thisJoinPoint, dao")
>
>
> 2010/7/13 Stephen Boesch <java...@gmail.com>
>
> The development process for aspectj is proving to be very cumbersome /
>> slow for a non-adept. I'd like clear understanding of the selection process
>> of pointcut's, to know what's going on and why my pointcut expressions are
>> not performing as expected.
>>
>> What are options for tooling?
>>
>> Also, should I move away from @AspectJ and use the traditional ajc
>> compiler to get more information and better support?
>>
>
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>
_______________________________________________
aspectj-users mailing list
aspectj-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/aspectj-users
