Here are the install instructions for Apache SOAP. 
 
========================================== 
 
First, how to build Apache SOAP 
 
Step 1: Make sure Apache Ant is properly installed on your system. 
 a. Download Apache Ant from <http://jakarta.apache.org/ant 
 b. Set ANT_HOME to the location where Ant has been 
installed 
 c. On Windows platform, add %ANT_HOME%\bin to your system 
Path 
 
Step 2: Download mail.jar, activation.jar, xerces.jar 
 a. mail.jar == <http://java.sun.com/products/javamail/ 
 b. activation.jar == 
<http://java.sun.com/products/beans/glasgow/jaf.html 
 c. xerces.jar == <http://xml.apache.org/xerces 
 
Step 3: Add mail.jar, activation.jar, xerces.jar, and servlet.jar (from 
Tomcat) or j2ee.jar (from Sun) 
 to your classpath. 
 
Step 4: From the xml-soap\java directory, run "ant dist". 
 
Windows Example: 
 
 d:\set ANT_HOME=d:\java\ant 
 d:\set PATH=%PATH%;%ANT_HOME%\bin 
 d:\cd java\xml-soap\java 
 d:\java\xml-soap\javaset 
CLASSPATH=%CLASSPATH%;d:\java\mail\mail.jar;d:\java\activation\activation.j 
ar;d:\java\xerces\xerces.jar; 
 d:\java\tomcat\common\lib\servlet.jar 
 d:\java\xml-soap\javaant dist 
 <!-- Ant output -- 
 
To enable optional support for BSF, POP3, SMTP, EJB, SSL, and JUnit, you 
need to add the appropriate packages to your classpath prior to running 
Ant to build to package. 
 
Requirements listed from the Apache SOAP Documentation: 
Java 1.1 or higher, and a servlet engine supporting version 2.1 or higher 
of the Java Servlet API 
A JAXP compatible, namespace aware XML parser (e.g. Xerces) 
JavaMail (mail.jar) and the JavaBeans Activation Framework (activation.jar) 
XMI encoding requires use of Java 1.2.2 and XML4J 2.0.15. Your classpath 
must have xerces.jar first and then xml4j.jar next in that order. 
Implementing services in scripting languages requires the use of Bean 
Scripting Framework. 
SSL (HTTPS) support requires Java 1.2.1 or later and the Java Secure 
Socket Extension. 
The SMTP transport requires the SMTP and POP3 Bean Suites. 
 
First, how to install Apache SOAP 
============================ 
The Apache SOAP documentation provides all of the information needed to 
get Apache SOAP up an running on a variety of application servers.- 
<http://xml.apache.org/soap/docs/install/index.html 
 
These instructions tell you exactly how to set up the classpath for each 
server environment. 
 
At runtime, your application must also be installed into the Server or 
SOAP classpaths. The classes must be visible to the SOAP Webapp so you 
need to either add the application jar to the servers classpath (how to do 
this is specific to each application server so follow the instructions 
provided by the server) or add the application jar to the SOAP Web 
application by adding the Jar to the soap/WEB-INF/lib directory or adding 
the classes to the soap/WEB-INF/classes directory. 
 
Example: 
 
I have Apache SOAP installed as an Apache Tomcat Webapp: 
d:\java\tomcat\webapps\soap 
I will add my specific Web service to Apache SOAP by copying myApp.jar to 
d:\java\tomcat\webapps\soap\web-inf\lib and then use the Apache SOAP 
deployment tool to deploy the Web service (see the Apache SOAP 
documentation for information on how to deploy services) 
 
An alternative approach is to embed Apache SOAP into your own Web 
application. To do so, simply add soap.jar, mail.jar and activation.jar 
(plus any additional optional features you are using) to your Web 
applications web-inf\lib directory and copy the soap.xml configuration 
file to web-inf. (soap.xml is used to configure the Apache SOAP runtime). 
 
Example: 
 
AddressBook.war 
 |--- (my JSP and otherfiles) 
 |--- META-INF 
 | |--- (manifest) 
 |--- WEB-INF 
 |--- soap.xml 
 |--- web.xml 
 |--- classes 
 | |--- (my application class files) 
 |--- lib 
 |--- soap.jar 
 |--- mail.jar 
 |--- activation.jar 
 |--- (other optional jar files) 
 
Note: when reading through the installation instructions provided by 
Apache SOAP, pay special attention to the details about how to install 
Xerces.jar if that is the XML parser that you are using. Many Web 
Application Servers ship an XML parser that gets in the way of any others 
that you may want to use unless you make specific changes to the 
application servers configuration. The Apache SOAP installation 
instructions will guide you through those changes. 
 
To run Apache SOAP on the client side, you must have, at a minimum, 
soap.jar, mail.jar and activation.jar in your classpath. If you are using 
any of the optional features (e.g. BSF, XMI, POP3 etc) then you must also 
have the corresponding JAR files in your classpath (see build instructions 
above). 
 
If you run into any problems, check out the troubleshooting page at 
<http://xml.apache.org/soap/docs/trouble/index.html. Most of the commonly 
occuring problems are dealt with there. If the problem you are facing is 
not addressed, post a note to the SOAP Users mailing list 
(<http://xml.apache.org/soap/mail.html)