1.4.4(Mar 2022)

Defects

The following defects are resolved in this build.

NXPSR-11250 : Support private local JVM for use when running application

Sometimes application may require a a particular version of the JVM. While there is an option to download from remote server, this feature will provide an option to use local JVM.

Set parameter java_local_path to point to local jre in runNexaweb.jsp (.nexaweb ) file.
This will run the application from the local JVM path.

For eg.

Launcher will run the application with JVM in the following order.

1. Local java path
   java_local_path=C:\Program Files (x86)\Java\jre1.8.0_111

2. Custom jvm,
   java_location = [windows] java_windows.jar
   Jre is downloaded from the remote server into .nexaweb<app>\java_vm folder

3. JVM Bundled with nexaweb launcher
   For eg. C:\Program Files (x86)\Nexaweb\NexawebLauncher\jre

4. System jre

You can specify if an exact version of the JVM is required by using
i. Setting java_exact_version_required = true and provide java_min_version

OR
ii. Setting java_min_version and java_max_version to the same value.

When exact version is required, launcher will try to find the java_min_version in the order above. If exact version is not found, it will popup error message and application is not started.

NXPSR-11252 : 1.4.2 and 1.4.3 console messages is different when creating a digest file

Message when creating digest files is changed back to 1.4.2 messages.

Message in 1.4.2 :

Message in 1.4.3: