commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kohsuke Kawaguchi <>
Subject [javaflow] a problem in ResourceTransformer abstraction
Date Tue, 27 Dec 2005 19:01:37 GMT

I found a problem in the current ResourceTransformer abstraction.

Sometimes, a proper instrumentation of a class requires information 
about other classes. Consider the following code:

   // note that in bytecode, type of local
   // variables aren't available
   var x;

   if(...) {
     x = new Foo();
   } else {
     x = new Bar();


   if(...) {
     new Thread(x);
   } else {
     new TreeSet(x);

Proper stack frame restoration at "someMethodCall" requires an 
identification of the common base class between Foo and Bar (so that an 
object of the right type will be set to local variable 'x'), which in 
turns requires information about Foo and Bar.

The current ResourceTransformer just takes the class file image to be 
transformed, and therefore a ResourceTransformer implementation is 
supposed to magically resolve Foo and Bar to the right class file --- 
which is impossible.

This is breaking my workflow engine that uses multiple class loaders 
(where 'Foo' may resolve to different symbols, depending on the context.)

So I suggest we introduce a mechanism to resolve symbols to their class 

   interface ClassImageLoader {
     byte[] load(String className);

... and change ResourceTransformer as follows:

   interface ResourceTransformer {
     byte[] transform(String className, ClassImageLoader loader);

Can I make this change?

P.S. Also how stable is the ASM implementation? Should we concentrate 
our effort on that side going forward?
Kohsuke Kawaguchi
Sun Microsystems         

View raw message