Contents

• Read This Section First
• What This Release Includes
• New And Updated Features
• Current Limitations

Read This Section First

Deploytool will help the user deploy web applications to the Tomcat server. If you are new to Tomcat, you will want to consult the Tomcat Documentation included with this release.

What This Release Includes

The Java^TM Web Services Developer Pack includes the deploytool that will help you package, configure, and deploy your web application to the Tomcat Web Server.

New and Updated Features

In previous the version of the Java^TM Web Services Developer Pack , developers had to manually deploy a web service or web application by placing the web application archive (WAR) file into the "webapps" directory of Tomcat. The user also had to manually create the web.xml to configure the web application. Now the user can use the deploytool to perform the following operations:

• Packaging - The user can use deploytool to package their web application files into a WAR.
• Configuration - The user can use deploytool to configure the web application by using the New Web Component wizard in the tool to automatically generate the web.xml file.
• Verification - The user can use the Verifier in deploytool to verify that the configuration is correct
• Deployment - The user can use Tomcat to deploy the web application to the Tomcat Server.

Current Limitations

• Deployment of WAR files written into the Tomcat webapps directory - The user will not be able to use deploytool to deploy a WAR file that was placed in the Tomcat webapps directory. The reason for this is because Tomcat considers a WAR file placed in the webapps directory as deployed, thus if the user tries to use deploytool to deploy it again, Tomcat will send an error back saying that the web application is already exists.
• Servlet/ClassLoader Error - If a servlet depends on code in an external WAR/JAR/.class file not included with the standard deploytool WARs, then the user must also bring in these external objects into deploytool in order to create the servlet component, otherwise the deploytool will display a no class definition found error.
• Database Applications - The user must select the corresponding Resource Reference/JNDI Name that he/she created in Tomcat otherwise, the database application will not be able to query the correct database.
• JAX-RPC Endpoint Default Settings - If the user first includes servlets or jsps as web components before inputting a JAX-RPC Endpoint by using a 'Edit Web Application' menu option, the user must then use the JAXRPC Settings button in the inspector front panel to add the JAX-RPC Default Settings.
• JAX-RPC Model File - If the user would like to include a JAXRPC Model File in their JAX-RPC Application, then this file must end with .xml.gz.
• JAX-RPC Custom Settings - If the user selects to use custom settings, he/she should not return to the endpoint screen before pressing finish and change the endpoint name, because this may cause the generated model file name in the xml viewer to be out of sync.
• JAX-RPC Endpoint Alias - The JAX-RPC Endpoint Alias should begin with a forward slash, otherwise Tomcat may throw a parser validation error when try to run the application.
• Deploytool Temporary Directory - The user can specify a the temporary directory that deploytool uses for file processing. If the user does not specify this, deploytool will create this directory. The user must not try accessing this directory while executing deploytool commands or putting their own files or links to other directories in this directory because this directory is recursively cleaned by deploytool.
• Deleting WAR files - Do not delete a WAR file from disc that deploytool has open. Deploytool give a warning message if this occurs.

Latest Release Notes

http://java.sun.com/webservices/docs/1.0/ReleaseNotes.html