• wrapper.java.command property
• wrapper.java.command.resolve property

Compatibilidad :	1.0.0
Ediciones :
Plataformas :

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.

wrapper.java.command=java

wrapper.java.command=%JAVA_HOME%/bin/java

wrapper.java.command=c:/j2sdk1.4.0/bin/java

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.

Windows:

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 the Sun JRE specified in the default registry key. It is possible to configure a specific JAVA_HOME location using the wrapper.registry.java_home property.

wrapper.java.command=

If the Java command is located using the Windows registry, the path to the command will be stored into a WRAPPER_JAVA_HOME environment variable. This value can then be referenced in the values of other properties.

Compatibilidad :	3.5.4
Ediciones :
Plataformas :

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 application 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.

wrapper.java.command.resolve=true

• wrapper.java.command (1.0.0)

  Establece la ruta al ejecutable de Java.

• wrapper.java.command.resolve (1.0.0)

  Especifica si el Wrapper debe intentar resolver el comando especificado de Java o continuar usando la ruta no resuelta como posiblemente definida.

• wrapper.java.command.loglevel (3.1.2)

  Controla en qué nivel de registro se registrará la línea de comandos generada.

• wrapper.java.detect_debug_jvm (3.3.6)

  Habilita la detección de un depurador en la línea de comandos.

• wrapper.java.version.fallback (3.5.38)

  Especifica un valor de reserva que se utilizará cuando la versión de Java no se haya analizado.

• wrapper.java.version.max (3.5.35)

  Especifica la versión máxima de Java para la cual el Wrapper puede iniciar la aplicación Java.

• wrapper.java.version.min (3.5.35)

  Especifica la versión mínima de Java para la cual el Wrapper puede lanzar la aplicación Java.

• wrapper.java.version.output (3.5.17)

  Muestra la versión de la JVM utilizada por el Wrapper.

• wrapper.java.version.timeout (3.5.27)

  Configura el número de segundos permitidos para que el proceso hijo imprima la versión de JVM antes de que se termine.

• wrapper.registry.java_home (3.2.4)

  Especifica una clave de registro que contiene la ruta de acceso a la carpeta principal de Java.

• wrapper.registry.java_version (3.5.36) ( Estándar/Profesional )

  Especifica una versión del JRE que se debe usar al ubicar el comando Java desde el registro de Windows.