[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [aspectj-users] Confused by cflow interaction
|
Keith,
Thanks, I was going to ask you to confirm this. Basically, the
visualizer in AJDT doesn't do a cflow analysis when indicating which
join points may be advised. Thus if I have:
call(public void get*(..)) && cflow(execution(something else))
the visualizer would show all getters in the application.
I thought I remembered seeing a TODO item for adding static cflow
analysis to the AJDT visualizer, but I couldn't find it after a cursory
search of the eclipse site. (I didn't check bugzilla).
Hope you're enjoying the book. Let me know if you have any other
questions.
Nick
On Mar 28, 2004, at 2:33 PM, Keith Sader wrote:
Sorry I didn't make this clear in the first post, but the aspects
themselves only advise their stated pointcuts, its just that the
visualizer shows the advice acting on other (wrong) pointcuts.
thanks,
Keith S.
Nicholas Lesiecki wrote:
Keith,
I'll see if I can take a look at this over the weekend and get back
to you.
Nick
On Mar 26, 2004, at 1:53 PM, SADER, KEITH D (CONTRACTOR) wrote:
<snip examples>
When I build this in Eclipse 2.1.3 using ajdt 1.1.4 it shows that
not only does this aspect advise my Flow class, but it also advises
other System.out.prinln() calls in other classes and aspects as
shown in the aspect view after doing a 'Project | Rebuild All'
I would have thought that the matchPrint() joinpoint would have
excluded any System.out.println() call that didn't occur within a
method "two()" (two() isn't defined for any of my other classes).
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/aspectj-users
