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 run.nexaweb runNexaweb file for launching Nexaweb web application
   

   The way to create Nexaweb web application is by using a run.nexaweb 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:
      

...

    e. Run the project on a web server, go to the URL: http://localhost:8080/nxRunNexaweb/runNexaweb, and save run.nexaweb runNexaweb

2. Digest the jars and create digest.txt and digest2.txt and upload them to the nexaweb application

           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 run.nexaweb runNexaweb in a different name. After generating the digest files, they need to be added into WebContent directory too as the jars.

    a. Create a local folder called "target". Copy getdown-1.7.1-SNAPSHOT.jar from Nexaweb Launcher installation folder and paste it into the target folder

    b. Copy the run.nexaweb runNexaweb file at step #d2 into this target folder 

    c. Create a "digesters" sub-folder under this target  and again copy run.nexawebfolder, copy runNexaweb file into this folder. Change its name , and then rename it to getdown.txt (Note: please check if the file extension is .txt after changing the name renaming)

    d. Copy NexawebImages.jar, and NexawebStandaloneClient.jar in the digesters directory

    e. Copy all jars other than above jars in into the ClientClassLoader directory, and the digesters directory looks as below:

...

                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 needs of need any jars other than NexawebImages.jar ,  and

               NexawebStandaloneClient.jar, you don't need to create a ClientClassLoader directory.

...

           f. Run the command below in command lines below:

             1)  1  Change the command prompt to the  D:\target folder

               2). Run command -  java -classpath getdown-1.7.1-SNAPSHOT.jar com.threerings.getdown.tools.Digester digesters

            Note: "D:\target" is the directory where getdown-1.7.1-SNAPSHOT.jar is put in and "digesters" is the directory to be digested in the above command             and it command. This command creates two digest files as the screenshot below: 

...

 a. Start the server which was configured for the Nexaweb project
 b. Double click run.nexaweb runNexaweb in the target folder to launch the Nexaweb web application   

...

1. Open the app directory. It is in  %systemdrive%%homepath%%SystemDrive%%HOMEPATH%/.nexaweb_<Server>_<Port>_<Application>_ .
   Note: the dots(.) in the server and application are replaced with underbar(_) . For example, the app directory: C:\Users\xuchen\.nexaweb\nxwb127_0_0_1_8080_myPrj4_ , where 127_0_0_1_ is the server 127.0.0.1 replaced . with _ , 8080 is port, and myPrj4 is application name 
2. Create a  file debug.txt on it
3. Relaunch the nexaweb web application, and the console.log will be created to catch all standard outputs   

...