Using the BootClasspath -- Tweaking the Java Runtime API Export

@inproceedings{citeulike:600782, abstract = {Many Java programmers don't realize it, but the Java Runtime Environment is an amazingly configurable environment-so much about the Java execution environment can be controlled via options either on the command-line or through the JNI Invocation interface. One such option is the ability to define the location of the Java "bootstrap" classes-java.lang.Object, java.lang.Exception, and so forth-to come from someplace other than the ubiquitous "rt.jar" file in the "jre/lib" directory. In fact, we can use this non-standard JVM option to subvert the Java environment in many powerful ways, giving Java programmers a tremendous amount of power over their environment. But with power comes complexity, and this is no exception: it's powerful, but only if you're willing to accept the risks that go along with it.}, citeulike-article-id = {600782}, citeulike-linkout-0 = {http://www.javageeks.com/Papers/BootClasspath/index.html}, keywords = {boot, classpath, compiler, java}, posted-at = {2006-04-26 00:53:51}, priority = {3}, title = {Using the BootClasspath -- Tweaking the Java Runtime API}, url = {http://www.javageeks.com/Papers/BootClasspath/index.html} }

TY - CONF ID - citeulike:600782 L3 - citeulike-article-id:600782 N2 - Many Java programmers don't realize it, but the Java Runtime Environment is an amazingly configurable environment-so much about the Java execution environment can be controlled via options either on the command-line or through the JNI Invocation interface. One such option is the ability to define the location of the Java "bootstrap" classes-java.lang.Object, java.lang.Exception, and so forth-to come from someplace other than the ubiquitous "rt.jar" file in the "jre/lib" directory. In fact, we can use this non-standard JVM option to subvert the Java environment in many powerful ways, giving Java programmers a tremendous amount of power over their environment. But with power comes complexity, and this is no exception: it's powerful, but only if you're willing to accept the risks that go along with it. TI - Using the BootClasspath -- Tweaking the Java Runtime API KW - boot KW - classpath KW - compiler KW - java UR - http://www.javageeks.com/Papers/BootClasspath/index.html ER -