I don't think I have much to add. My thought process is
1. Verify that the class file you think is being loaded as the service really is the
one being loaded by deleting it, restarting the servlet container, and having the
client get an error that the class could not be found.
2. Restore the class file to its location and get the "no signature match" error.
3. Disassemble the class file to verify that the signature *does* match that which is
expected.
4. At this point, you know you have a class loader problem, specifically that Apache
SOAP classes are being loaded by multiple class loaders within your servlet container.
Again, the only place the Apache SOAP classes should be loadable by the container is
from the Apache SOAP webapp, which usually means they are in subdirectories of
.../webapps/soap/WEB-INF/classes (the exact path with vary by container). There
should be no Apache SOAP classes in any of the other directories from which the
container loads classes, no should soap.jar be in $JAVA_HOME/lib/ext or
$JAVA_HOME/jre/lib/ext.
5. If you still don't see the cause of the problem, you can post the following to this
list for more help
- OS
- JDK/JRE version
- servlet container and version
- Apache SOAP version
- steps followed to deploy the Apache SOAP webapp
- steps followed to deploy the service classes
Scott Nichol
Do not send e-mail directly to this e-mail address,
because it is filtered to accept only mail from
specific mail lists.
----- Original Message -----
From: "tony vieitez" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 24, 2003 6:12 PM
Subject: null pointer exception
> I've just done what you suggested Scott and still no luck. I have
> already successfully implemented and run a soap-rpc application which
> may suggest that the configuration of the system is not an issue. Not
> too sure about this though.
>
> Tony
>
>
