RE: [aspectj-users] About join points for local variables.

["Ron DiFrango" <rdifrango@xxxxxxxxxxxxxxxxxxx>]

Sunny,
 
If a local variable is an object, you could trap the creation of the object via something like:
 
call(*.new(..))
 
The you could use standard reflection to see which object you are in.
 
For parameters into methods you, can use generic around advice:
 
aspect Logging {
     before(): within(com.bigboxco..*) && execution(public * *(..)) {
         System.err.println("entering: " + thisJoinPoint);
         System.err.println("  w/args: " + thisJoinPoint.getArgs());
         System.err.println("      at: " + thisJoinPoint.getSourceLocation());
     }
}
 
See the JavaDoc for the runtime API:
 
http://www.eclipse.org/aspectj/doc/released/runtime-api/index.html
 
Ron

________________________________

From: aspectj-users-bounces@xxxxxxxxxxx on behalf of Sunny
Sent: Thu 4/6/2006 1:10 PM
To: aspectj-users@xxxxxxxxxxx
Subject: [aspectj-users] About join points for local variables.


Dear Folks,
 
After reading the AspectJ FAQ No. 21: "Why can't AspectJ pick out local variables (or array elements or ...)?"
 
I have the following question:
 
What I would like to do is to dynamically maintain an object graph (directed), where nodes represent runtime objects and directed edges denote reference relationships between objects. Apparently an object can refer to other objects not only through its fields, but also through its local variables or parameters. Without join point for local/parameters, how would I accurately obtain the current system state info (in terms of relationships between objects)? 
 
Is there any other way that I can achieve the same goal? I appreciate your help!
 
Sunny

<<winmail.dat>>