Hi All



Hopefully someone can help me.

We are having an issue with Applications that use different versions of Java 2 Runtime Environment.

If we SMS out a package that uses JRE 1.4.2_xx and then sms out an app that installs JRE 1.3.1_01 the 1.4.2 apps stop working. Reversing the order of the JRE installs fixes this but as these apps are SMSed out we cannot rely on order of installation.

We have a preloader that prepends the JRE path to the PATH Enivironment Variable which has historically fixed all our Java clashes before (previous clashes were all between 1.1.8, 1.3.1 and 1.4.1) – but doesn’t work in this case.

Has anyone solved this problem before?
Thanks for any help anyone can give me.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Although different versions of the JRE use different folders, there are still a couple of conflicting rsources between versions.

As I remember, they put a copy of "java.exe" in "%SystemRoot%\System32\", and some kind of "currentversion" key under "HKLM\Software". If you're going to have several java packages in your environment, you need to design those packages to be "aware" of the other versions. Also, beware when repackaging applications that install a JRE version as a dependency - capturing this by "mistake" is quite common!

From a command window, I think there's a command something like "java -ver" to determine the version?

Sorry this is a bit vague - it's been a while, and I don't have a JRE installed.
Answered 02/14/2005 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
0
This might be useful too:

http://www.javageeks.com/Papers/MultipleJavaHomes/index.html
Answered 02/14/2005 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
0
Yeah Java.exe and Javaw.exe are definately not version stamped and cause issues if you do not install oldest to newest. Also there are some COM registrations and system default markers in the registry that will change. I used to have a list but making the list is easy to do.

Install the 1.4.1 engine then install a 1.3.1 engine. Start your snapshot here. Take the 1.4.1 engine and reinstall it then end the capture. You should then see what I am talking about in the registry.

What I had to do in the last client site I was on was write an application that talked to Active Directory and determined the latest Java version they had been assigned. I would then have the application call a Wise 9 installer to copy down the right versions of Java.exe and Javaw.exe as well as populate the registry.
Answered 02/14/2005 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity