Known issues - Java technology

Working with JavaFX in Java 11

To use OpenText Functional Testing for Developers with JavaFX applications in Java 11, perform the following steps on the computer running your application:

  1. Download the JavaFX module from the Gluon site and store it locally.

    Caution: Make sure the path to the JavaFX module does not contain any spaces.

  2. Set the following environment variables.

    • PATH_TO_FX = <JavaFX module location>\lib.

    • In PATH, add %PATH_TO_FX%.

    • JDK_JAVA_OPTIONS = --module-path %PATH_TO_FX% --add-modules=javafx.controls,javafx.fxml,javafx.base,javafx.swing,javafx.media --add-opens javafx.graphics/com.sun.glass.ui=ALL-UNNAMED --add-opens javafx.base/com.sun.javafx.event=ALL-UNNAMED --add-opens javafx.graphics/com.sun.javafx.stage=ALL-UNNAMED --add-opens javafx.graphics/com.sun.javafx.scene=ALL-UNNAMED --add-opens javafx.base/javafx.event=ALL-UNNAMED --add-opens javafx.graphics/javafx.stage=ALL-UNNAMED --add-opens javafx.graphics/javafx.scene=ALL-UNNAMED

Working with JavaFX in Java 12 or later

To use OpenText Functional Testing for Developers with JavaFX applications in Java 12 or later, perform the following steps on the computer running your application:

  1. Download the JavaFX module from the Gluon site and store it locally.

    Caution: Make sure the path to the JavaFX module does not contain any spaces.

  2. Set the following environment variables.

    • PATH_TO_FX = <JavaFX module location>\lib.

    • In PATH, add %PATH_TO_FX%.

  3. We recommend not running a command line window and your application at the same time. Therefore, launch the application from a batch file instead of using a command line that specifies the module path and dependencies:

    In the folder containing your application's .jar file, create a .bat file containing the following command: 

    start javaw --module-path="%PATH_TO_FX%" --add-modules={all modules required by your application} --add-opens {specify opens for modules if required} -jar <Application_Name>.jar

    Example:

    start javaw --module-path="%PATH_TO_FX%" --add-modules=javafx.controls,javafx.fxml,javafx.base,javafx.swing,javafx.media --add-opens javafx.graphics/com.sun.glass.ui=ALL-UNNAMED --add-opens javafx.base/com.sun.javafx.event=ALL-UNNAMED --add-opens javafx.graphics/com.sun.javafx.stage=ALL-UNNAMED --add-opens javafx.graphics/com.sun.javafx.scene=ALL-UNNAMED --add-opens javafx.base/javafx.event=ALL-UNNAMED --add-opens javafx.graphics/javafx.stage=ALL-UNNAMED --add-opens javafx.graphics/javafx.scene=ALL-UNNAMED -jar JavaFX.jar

    Save the .bat file and run it.

Installing Java on a Windows machine with OpenText Functional Testing for Developers

When re-installing or upgrading the JRE on a Windows machine with OpenText Functional Testing for Developers installed, you might encounter error 1603 preventing the JRE installation to complete.

This can be caused by an interference between the OpenText Functional Testing for Developers Java environment variables and the Java installer.

To successfully complete the installation, rename the OpenText Functional Testing for Developers Java environment variables, perform the JRE installation and restore the variable names.

To temporarily rename the Java environment variables: 

  1. On your Windows Desktop, right-click My Computer or This PC and select Properties.

  2. Select the Advanced tab.

  3. Click the Environment Variables... button.

  4. Look for the following environment variables both under the user variable list and the system variables list and edit their names:

    • _JAVA_OPTIONS

    • Java_Tool_Options

    • IBM_Java_Options

  5. Install the JRE.

  6. After the installation completes, change the environment variables names back to their original names.

Java 9

When working on Mac versions Sierra or later, the runtime engine tray icon is not displayed. To start and stop the runtime engine and to open the Settings dialog box, use command line scripts as described in the relevant topics. For details, see Customize the runtime engine settings and Start/Stop the runtime engine.

See also