Correctly shipping a web service client library

From: Ryan Champlin <>
Date: Thu, 7 Apr 2005 15:46:13 -0500

I'm building a web based application that is using a web service we developed for our application. Basically, for my web based application I am using JAX-RPC to generate my client stubs for my web service. If I deploy my web application with these stubs what else will need to ship with my web application? The web service will not be packaged with this particular web application. Can I just package up all the stubs in a jar file and then reference that from my web application and have everything work fine? Obviously all the JAX-RPC jars will need to exist on whatever webserver/servlet container the web app is being run on for this to work. Will J2EE 1.4 based servlet containers contain these JAR files already? I assume not as Tomcat doens't ship with them as of yet.

If a customer were to try to deploy them on another server say a Weblogic would they have these JARs or should I always be shipping all of them along with my web app that has the JAX-RPC client stubs.