"Unable to resolve namespace URI for 'xsd'".
Ensure that:
(a) You are using Xerces 1.4.4, 1.4.3, 1.2.3 or 1.3.0 (but NOT 1.3.1) - on both the client and the server (if both are using Apache-SOAP).
(b) xerces.jar is the FIRST entry in your CLASSPATH, as described in the Apache-SOAP installation instructions.
(c) There is ONLY ONE version of xerces.jar in your CLASSPATH.
(d) There are no other XML parsers in your classpath. Some people have experienced this problem due to an early version of the JAXP package hiding in JAVA_HOME/jre/lib/ext.

Eventually, download and install latest versions of xerces.jar and jaxp.jar

DevX Tech Tips: Obtaining a File Path From a Class Name
You can use a basic class finder utility to find the actual class file from a class.

DevX Tech Tips: A Basic Class Finder Utility
Here's a useful utility for finding the full pathname for a class (or any other file) from a Java program.

Deploying a service
Win32 > deploy.bat C:\soap\soap-2_2\samples\addressbook\DeploymentDescriptor.xml

java/lang /noClassDefFoundError org/apache/soap/soapException
Make sure that 'soap.jar' from "eservices/lib" is included in your classpath. This includes having this class in your oc4j environment (for example setting it in application.xml under config directory).

Apache-SOAP User's FAQ: "Element must contain a:'faultcode' element"
This is probably due to a bug in some newer releases of Xerces (e.g. 1.3.1). Try using Xerces 1.4.3, 1.2.3 or 1.3.0 instead (on both the client AND the server) - have a look on http://xml.apache.org/dist/xerces-j/. You should also make sure that xerces.jar is the FIRST entry in your classpath.

resin-interest: FW: Erronous stackTrace namespace
If I look at the message with a tcp tunnel I find the problem