Page Comparison

Oracle announced that the Java Applet and Web Start functionality, including the Applet API, Java plug-in, Java Applet Viewer, JNLP and Java Web Start including the javaws tools are all deprecated in JDK 9 and will be removed in a future release. As an alternative, our customers are recommended to use the Nexaweb Launcher to deploy and  run Nexaweb web applications. 

This step-by-step guide shows how to perform the migration of Nexaweb application to Nexaweb launcher.

Prerequisites:

...

You can find the installers at the Nexaweb download page. 

Step-by-step guide

To deploy a Nexaweb application using Nexaweb Launcher, the recommended approach is to use the Nexaweb Standalone Client. Here are the steps:

1. Create a runNexaweb file for launching Nexaweb web application
   

   The way to create Nexaweb web application is by using a runNexaweb (Nexaweb Launching Protocol) file deployed on the server. When the user types the URL of a Nexaweb file in the browser, the application will detect that the response is a Nexaweb file and it will start Nexaweb  launcher to load the Web Start application according to the setting in the Nexaweb file. So a Nexaweb file needs to be created for the Nexaweb application.

   1. Download the latest version of Nexaweb Platform (4.5.65.0009 or later) and install it on the server
   2. Download and install Nexaweb Launcher on the client machine.
   3. Create a new Nexaweb application project
   4. Copy NexawebImages.jar,  NexawebStandaloneClient.jar,  and all other jars to WebContent directory as below:
      

...

           Nexaweb launcher uses Getdown’s digester to generate jar’s digest and use the digest to check if it needs to download a new version jar file or not. So the users need to digest all jars the web application needed
          and put them in the same directory with GetDown.txt which is just the same file runNexaweb in a different name. After generating the digest files, they need to be added into WebContent directory too as the jars.

...

                Note: the demo project uses an external jar called test.jar. It is put under ClientClassLoader directory, which is as below. If the project does not need any jars other than NexawebImages.jar and                NexawebStandaloneClient.jar, you don't need to create a ClientClassLoader directory.

...