Deploying an Applet as a WAR File

By default, you can run and debug web application components including applets in JDeveloper's embedded OC4J server before deploying the resulting WAR or EAR file to the target application server.

To deploy an applet as a WAR file:

If not already done, create a deployment profile for applets.
If not already done, create an application server connection.
The <webapp>.deploy deployment profile icon appears in the Navigator below the specified project. Select and right-click its deployment profile icon. The context menu displays these deployment options:
1. Deploy to <Name_of_server_connection>: the applet is packaged as a WAR. JDeveloper also generates an EAR file which contains the WAR before deploying to the selected application server connection which you created earlier.
2. Deploy to New Connection: Launches the Connection Wizard which lets you create a new application server connection.
3. Deploy to WAR file: the applet is packaged as a WAR and saved to the local directory or mapped network drive you specified earlier in the <webapp>.deploy profile settings.
4. Deploy to EAR file: the applet is packaged as an Enterprise Archive (EAR) file and deployed to the local directory or mapped network drive you specified you specified earlier in the <webapp>.deploy profile settings.
  Important: The deployed applet files must reside in a separate location from any other web application files you've deployed.
(Optional) If you want to edit either the <webapp>.deploy profile or its corresponding web.xml deployment descriptor settings, right-click its icon and choose Settings.

Note: If you encounter problems when deploying a Swing applet (JApplet), for example, the error "Class not found" is displayed, this may indicate that JDeveloper cannot locate the Swing libraries. You may need to force your clients to use Sun's J2SE browser plugin or bundle the Swing libraries for JVMs version 1.1 with your applet.