The command to use when launching a JVM.
If the full path to the Java executable is not specified,
then the Wrapper will attempt to locate a Java executable on the system path.
Example using system path:
Example using JAVA_HOME environment variable:
Example using full path (not platform independent):
Not contain an extension:
It is advised that the value does not contain an extension.
Specifying a value like java.exe together with an extension
would mean that the same configuration file could not be used on Linux/UNIX systems.
On Windows systems,
it is also possible to use the JRE configuration from the system registry.
In that case, this property is required to be set to an empty value.
By default, the Wrapper will look for a Sun JRE using the default registry key.
It is possible to configure a specific JAVA_HOME location using the
Example using system registry (not platform independent):
If the Java command is located using the Windows registry,
the JAVA_HOME value will be stored into a
WRAPPER_JAVA_HOME environment variable.
This value can then be referenced in the values of other properties.
This property specifies whether the Wrapper should try to resolve the Java command specified in
the wrapper.java.command property or continue using the unresolved path as possibly defined.
Resolving the Java command by the Wrapper is generally a good option, as it will help you to
point out and start troubleshooting easily missettings on the environment leading to unexpected behaviour
when starting your application with the Wrapper.
However, on some UNIX distributions a JVM can be started not only with the "java" command but also by
small helper applications, e.g. run-java-tool on Gentoo Linux.
However this applications might only allow to get called via a symbolic link to them.
The default value of this property is "TRUE".
If you want to deactivate the resolving, please switch this property to FALSE.