Hi: I just executed the self-extracting file from sun for Solaris: j2re-1_4_2_09-solaris-*.sh. I want to execute a different version of Java than is "formally" installed on my Solaris box. The installation went fine and when I execute
When I try and run one of my Java applications, I get:
I realize that there must be some interaction between the 1.4 Java launcer I just installed and the older (1.2) JRE "formally" installed. Can anyone tell me how I can get my newly installed (private) JRE to run? TIA! - Rolf. [ September 26, 2005: Message edited by: Michael Ernest ]
I'm not familiar with solaris, but on linux, I would check two things:
JAVA_HOME should point to the installed JDK (which is the parent of a jre, if you install it). Well - you're only talking about a JRE, not a jdk. Perhaps JAVA_HOME points to the older jre's parent dir?
JAVA_HOME is a convention used by many (not all) Java apps. If there's any time Java itself references this environment variable, I've never heard of it.
The JRE's library classpath is implicit and shouldn't be explicitly declared.
Normally, all that's required is to implicitly (via PATH) or explicitly (/usr/local/java/bin/java) invoke the java runtime to get things to work unless there's some sort of load library issue.
I'm really very disappointed in how Sun installs Java under SunOS. They made much better allowances for multiple JVM releases on Linux.
Incidentally, to get alternate JVMs into Solaris, I bend the Linux conventions to avoid the Solaris naming conflict by unpacking the JVM into a /usr/java.d directory. So for example, I can run JDK1.5.0 using the command /usr/java.d/jdk1_5_0/bin/java.
When it comes to destroying a civilization, gas chambers cannot hold a candle to echo chambers.