Description Navid Mehregani 2004-07-13 17:04:13 EDT

Consider the following probekit file:

<?xml version="1.0" encoding="ASCII"?>
<probekit>

   <!-- Entry and Exit fragments.  -->
   <probe>      

      <!-- Instance variables -->
      <fragmentAtClassScope>
         static public boolean trace = false;
      </fragmentAtClassScope>
                        
      <!-- Entry fragment of the instrumentation -->
      <fragment type="entry">
   
         <code>      
         	if (Should we trace?)
         	{
			trace = true;
         	}
         
         	if (trace)
         	{
			// Do the tracing
		}		
         </code>
      </fragment>
      
      <!-- Exit fragment of the instrumentation -->
      <fragment type="exit">

         <code>                 
         
         	if (trace)
         	{   
			// Do the tracing
		}
				        
         </code>
      </fragment>      

   </probe>   
   
   <!-- Call site probes for the JDBC methods -->
   <probe>
                       
      <!-- beforeCall fragment of the instrumentation -->
      <fragment type="beforeCall">
   
         <code>
		
		// I would like to use the trace boolean variable of the above probe to
determine if I should trace these calls
		
		if (trace)
		{
			// Do the tracing
		}
         </code>
      </fragment>
      
      <!-- afterCall fragment of the instrumentation -->
      <fragment type="afterCall">
 
         <code>           
		// I would like to use the trace boolean variable of the above probe to
determine if I should trace these calls
		
		if (trace)
		{
			// Do the tracing
		}
	         
         </code>
      </fragment>      

      
   </probe>
   
</probekit>

The above file contains two probes (one method probe and one callsite probe). 
As of right now, there is no way for these probes to "see" each other.  But the
above file illustrates a scenario where they need to "see" each other.

Looking at the Java class generated from the above probe, it should be
relatively simple to do this.  Each of the above probes correspond to a sub
class of a larger class created.  If there was some way in the XML code to
create an instance variable for this larger class, then there wouldn't be a
problem with completing the above task.  This can be in the simple form of
another tag specified in the <probekit> tag, but outside all the <probe> tags. 
This tag can then create instance variables for the class that contains all the
sub classes corresponding to the different probes.  The instance variables can
then be used by any of the probes, which in turn will allow them to share
information with each other.

Note that this defect is similar to defect RATLC00376855 created in the
Cupertino database.