How does Java resolve a virtual method at runtime? If a particular
virtual call site can have many potential targets because the object
could possibly be one of many types, what exactly goes on in the
machine to resolve this call? Is there a lot of overhead associated

I've created a C shared library (libSysEventProxy.so) that contains a
JNI wrapper that calls functions in another shared library
(libnetcomm.so); this shared library in turn calls functions in yet
another library (libnetgen.so). Thus, the static initializer in my Java

I have created an Event-Sink class in C++ to handle COM-Events and it
works well in a MFC-application.
But if I create a DLL to use this Event-Sink-Class with the JNI then
the callback function of the event-sink is not called. The COM-Server

I'm a little confused about the way java virtual machines maintains the
initiating class loader lists. Do VMs on every loadClass() invocation an
stack inspection or...?
Thanks!

We are in the step of selecting a new vm (embedded). The question is
which version of jdk it shall support. The battle stands between 1.4 and
1.3. I have not managed to find any benchmark statistics. Have anyone
else managed to find that information.