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, package the applet for deployment.
If not already done, create an application server connection.
In the Navigator, right-click the deployment profile and select one of the deployment options:
- Deploy to <most-recent>: the previous deployment is repeated.
- Deploy to: the applet is packaged as an EAR file containing a WAR file, and is deployed via the connection selected in the submenu. Choose New Connection to create a new application server connection.
- 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 deployment profile.
- 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 deployment profile.
  
  Important: The deployed applet files must reside in a separate location from any other web application files you've deployed.

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.