Hal Vaughan <hal@thresholddigital.com> writes:

interface Caller
{
}
class Callee
{
 public void callMe( Caller caller )
 {
   doSomethingWith( caller );
 }
}
class ACaller implements Caller
{
 public void someMethod()
 {
   Callee callee = new Callee();
   callee.callMe( this );
 }
}

I have a setting editor that edits data in tables depending on what is
selected in components.  This app will have a number of tab panels and each
tab will handle a different set of data.  I know I'll be adding tabs along
the way and I won't have time to recode each one.  I've written a number of
wrapper classes to work with all the Swing components.  I have one wrapper
for JComboBox that will have combined fields.  When a component wrapper
class calls to ask for its value, if it could check the calling component
and compare it to the list of registered components, then it could send
back the answer that registered component would use.

In other words, I might have three registered components and each one would
receive a different value when calling the same method.  Unregistered
components would always get the same value.

Hal

Tris Orendorff schrieb:

I can also give some nice example..

I use this for creating my log4j loggers: (idea came from Hein Kabutz)

private static final Logger logger = LoggerFactory.make();

and behind this make method is:

public static  Logger make(){
   Throwable t = new Throwable();
   StackTraceElement directCaller = t.getStackTrace()[1];
   Logger l = null;
   try {
       l =   Logger.getLogger(Class.forName(directCaller.getClassName()));

   } catch(ClassNotFoundException cnfe ) {
       l =  Logger.getLogger(directCaller.getClassName());
   }
       
   return l;
}