If JCP is invoked using JRE short path e.g. C:/progra~1/java/jre6/bin/javacpl, then one can notice 2 enteries against the 6u10 inside the Java Runtime parameters dialog. It is a automation blocker in the sense that runtime params set against C:/progra~1 JRE entry will be ignored and APIs under our STL library will consider C:/progra~1...... entry as default JRE since most of the times it ends showing up at index 0 i.e. first JRE enrty inside the JRE table

Steps to reproduce:
-----------------
1) Invoke JCP as C:\progra~1\java\jre6\bin\javacpl
2)GO to Advanced > Java > View
If you can notice 2 enteries aganist 6u10 JRE then bug is reproduced
Posted Date : 2008-04-22 19:27:38.0

N/A

A fix is to add a getLongPathName method so that all paths are converted to a long path name before comparison. On Unix platforms, the getLongPathName does nothing. Also, adding a samePaths method so that the comparison will be performed in a case insensitive way on windows platform.

The changes in CplLauncher.cpp is to fix the problem when the user start the Java Control Panel using short path and then selects "Java" -> "View" (under Java Applet Runtime Settings or Java Application Runtime Settings) and then cancel out all the way to exit the Java Control Panel. This scenario results in multiple entries of the same JRE in the deployment.properties file, i.e.
      deployment.javaws.jre.0.path=F\:\Program Files\Java\jre6\bin\javaw.exe
      deployment.javaws.jre.1.path=F:\progra~1\Java\jre6\bin\javaw.exe
Although the multiple entries of the same JRE don't affect the operation of Java Control Panel or running applets or web start apps., I think it's better to keep the deployment.properties file correct to avoid other side-effects.
Posted Date : 2008-04-25 23:17:56.0