To get a device up and running, it's nice to have the jit source (part of the jvm) to get stats and various information about the compiled sources. On devices with different type of resources, it's nice to know as much as one can about the runtime classes. In this case, derby would be the runtime classes.

So getting the sources for the jit would allow a multitude of information to be gathered that one normally could not do.

scott

Daniel John Debrunner wrote:

scott hutinger wrote:


I initiated looking for the jit sources. No feedback as of this current
time; and my thoughts are this is a needed thing.
Possibly some other persons need to look into this needed item.



What is the jit source?

Derby relies on a java virtual machine in order to function. The JIT is
part of the JVM, not part of Derby. For any embedded device use, e.g.
J2ME, the assumption is that the device provides a J2ME/CDC/Foundation
virtual machine.

Dan.






Reply via email to