Creating Java Client Web Archive for Java Web Start

You can use JDeveloper's J2EE web deployment process to set up the web server before downloading and running the application using Java Web Start.

Once the application resides on the web server, it becomes very easy to maintain. Java Web Start takes care of identifying and downloading application updates each time the user runs the application.

To create Java client applications for deployment to the web server:

Create a simple JAR archive of your Java client application.
Create a Web Start JNLP Definition for Java Clients to generate the JNLP file and HTML file for use with Java Web Start.
In the Navigator, select the <project name>.jpr in which you want to create the WAR deployment profile.
Choose File | New to open the New Gallery.
In the Categories tree, expand General and select Deployment Profiles. In the Items list, double-click WAR File - J2EE Web Module.
If the category or item isn't found, make sure the correct project is selected, and choose All Technologies in the Filter By dropdown list.
Click OK to create a WAR file which contains the JNLP file, the simple JAR file, and the HTML file.
Specify a location for the <webapp_name>.deploy profile or accept the defaults.
Click Save.
The WAR Deployment Profile Properties panel displays. Configure the settings for each page as appropriate. For more information, see Creating a Deployment Profile for Web Applications (WAR).
The newly created <webapp>.deploy deployment profile and its corresponding web.xml deployment descriptor icons appear in the Navigator below the specified project.
To deploy, see Deploying a Java Client Web Archive for Java Web Start.
(Optional) If you want to edit either the <webapp>.deploy profile or the web.xml deployment descriptor settings, right-click the profile and choose Properties.

By default, you can run and debug the WAR components in JDeveloper's embedded OC4J server to test the application. However, when you are ready to deploy the resulting WAR or EAR to the target application server, make sure to create an application server connection.

Notes:

The web module is deployed to the target deployment directory. See OC4J Deployment Application Directory Structure or refer to the Oracle Application Server Containers for J2EE User's Guide provided with the Oracle Application Server documentation library for information on the deployed location of the application files including the WAR and EAR files.
The web container in Oracle Application Server provides full support for Servlets 2.3 and JavaServer Pages (JSP) 1.2. For more information, refer to the Sun Microsystems Java Servlet Specification, Version 2.3 which you can download from java.sun.com/products/servlet/.
Make sure that the web application deployment descriptor is located inside the Web Application Archive (WAR) file WEB-INF/web.xml .