Eugene Kuleshov wrote:
I mentioned before analyzer is used here to compute stack and locals slots for method instructions in order to be able to restore/cast to correct types when restoring continuation.
Right.
Speaking about Ant, can you tell me how can I test this issue?
I guess I should write a test case. I think it's just a matter of writing a few classes that refer to each other, and then try to instrument them through the Ant task.
When instrumenting from Ant task, you don't want to load those classes that you are instrumenting into the Ant process. So any type computation based on java.lang.Class won't work (it's not just a matter of ClassLoader.)
> Or
maybe you can subclass SimpleVerifier yourself and overwrite following
method:
protected Class getClass(final Type t) {
try {
if (t.getSort() == Type.ARRAY) {
return getClass()
.getClassLoader()
.loadClass(t.getDescriptor().replace('/', '.'));
}
return getClass()
.getClassLoader()
.loadClass(t.getClassName());
} catch (ClassNotFoundException e) {
throw new RuntimeException(e.toString());
}
}
Eric, I actually wonder if we can use
getClass().getClassLoader().loadClass(...) (or
Thread.currentThread().contextClassLoader().loadClass(...)) instead of
Class.forName(...) method? Do you recall if there was some reasons to
use Class.forName?
-- Kohsuke Kawaguchi Sun Microsystems [EMAIL PROTECTED]
smime.p7s
Description: S/MIME Cryptographic Signature
