JAVA AND OLDJAVA
On Solaris systems, the java launcher tool comes in two variations: java, which implements all 1.2 features; and oldjava, a limited-feature launcher tool, which supports programming techniques that are incompatible with some 1.2 features. These are the differences between java and oldjava:
The oldjava launcher does not support the extension mechanism, though it can, of course, use extension packages as class and resource archives. The oldjava launcher uses the bootstrap class loader for all classes, while the java launcher uses the bootstrap class loader only for bootstrap classes. With java, the -classpath and -cp options specify a search path for user classes, and cannot be used to specify locations for bootstrap classes. With oldjava the -classpath and -cp options specify locations for all classes, including botstrap classes.
Note that java and oldjava do not differ in their use of the CLASSPATH environment variable. Unless overridden by -classpath or -cp, CLASSPATH always specifies the location of user classes, but says nothing about the bootstrap classes.
The oldjava launcher supports all the 1.2 security features. With oldjava, however, classes loaded from the class path will not have a protection domain and will therefore have all permissions which is true only for bootstrap classes with the java launcher.
This command using oldjava
oldjava -classpath <path> ...is equivalent to this command using java
java -Xbootclasspath:<path> -Djava.ext.dirs= ...where in both cases <path> contains the file rt.jar. (See the SDK FIle Structure document for a description of rt.jar and its location in the SDK software.)
On Solaris systems, the java launcher tool comes in two variations: java, which implements all 1.2 features; and oldjava, a limited-feature launcher tool, which supports programming techniques that are incompatible with some 1.2 features. These are the differences between java and oldjava:
The oldjava launcher does not support the extension mechanism, though it can, of course, use extension packages as class and resource archives. The oldjava launcher uses the bootstrap class loader for all classes, while the java launcher uses the bootstrap class loader only for bootstrap classes. With java, the -classpath and -cp options specify a search path for user classes, and cannot be used to specify locations for bootstrap classes. With oldjava the -classpath and -cp options specify locations for all classes, including botstrap classes.
Note that java and oldjava do not differ in their use of the CLASSPATH environment variable. Unless overridden by -classpath or -cp, CLASSPATH always specifies the location of user classes, but says nothing about the bootstrap classes.
The oldjava launcher supports all the 1.2 security features. With oldjava, however, classes loaded from the class path will not have a protection domain and will therefore have all permissions which is true only for bootstrap classes with the java launcher.
This command using oldjava
oldjava -classpath <path> ...is equivalent to this command using java
java -Xbootclasspath:<path> -Djava.ext.dirs= ...where in both cases <path> contains the file rt.jar. (See the SDK FIle Structure document for a description of rt.jar and its location in the SDK software.)
解决方案 »
免费领取超大流量手机卡，每月29元包185G流量+100分钟通话, 中国电信官方发货