Automated Installer Script Does Not Recored Preferred JRE

**Issue originally submitted through Bugzilla (Bug #736128)**

Description of problem:
Automated installations of JBDS fail on Windows due to the preferred JRE
location not being recorded by the graphical installer for reuse in cases where
the preferred JRE is not also on the PATH.

Version-Release number of selected component (if applicable):
4.1.0.GA

How reproducible:
Easily reproducible.

Steps to Reproduce:
1. Install Java on Windows, but do not add to PATH (this simulates a Java
install that is not in the user's PATH, such as a preferred Java version, or
other Java setup) [or remove Java from the user's PATH].
2. Run the graphical installer for JBDS 4.1, being sure to indicate the
location of the JRE you wish to use to run JBDS.
3. Copy out the InstallConfigRecord.xml from the installed JBDS directory for
use later.
4. Note: this file does not include any setting for the selected Java JRE that
was used during the install.
5. Uninstall JBDS.
6. Re-install JBDS using the command java -jar jbdevstudio*.jar
InstallConfigRecord.xml to run an automated install.
7. Attempt to start JBDS, and get an issue with a missing JRE, because said JRE
is not on the PATH or in the JBDS install directory.

Actual results:
JBDS fails to start.

Expected results:
JBDS starts with the user-selected JRE.

Additional info:
Obviously, we can work around this by adding the JRE to the PATH on Windows,
but we should be able to respect the installer's setting in the recorded
script, rather than ignoring input from the user.

I've set this to low priority.

The same process works fine on vanilla Red Hat Enterprise Linux, presumably
because the install of Java via RPM automatically adds the Java executables to
a user's PATH (installs to /usr/bin, or the like).