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 c
Try running the soap-rpc app that you know works!?!
See if it will run here.
Could help!
Jtony vieitez <[EMAIL PROTECTED]> wrote:
I've just done what you suggested Scott and still no luck. I havealready successfully implemented and run a soap-rpc application whichmay suggest that the configu
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
After deleting the other soap.jar, did you restart your servlet container?
Have you made sure that the classes from within soap.jar are not exploded somewhere
(other than your webapp)?
Are you sure you compiled your class against soap.jar and had no "local" definition of
Envelope or SOAPContext
Hi
Scott
Thanks
for your ideas. I did have a number of soap.jars and
after searching my system I found and placed them into the recycle bin along
with other versions of xerces and xalan
but still the 'no signature match exception' remains.
Tony
Did you change the server environment any? In particular, did you copy the soap.jar
somewhere new? You should only have a single place from which your servlet container
can load the Apache SOAP classes, and it should be the webapp into which you deployed
Apache SOAP. Different locations from
Hi
guys
Thanks
for your insightful responses - but now my problem has moved on somewhat. I
have left behind (or maybe now not yet reaching!) the null pointer exception
and am now experiencing a 'no signature match exception':
Exception
while handling service request:
altituderespons
A couple of things:
1. Is this really a single line in your deployment descriptor? There is a 'feature'
that may give an NPE when there is whitespace as part of this element.
org.apache.soap.server.DOMFaultListener
2. You create your document using
Document doc = new org.apache.xerces.d
Null pointer exception sounds like something going wrong with the
service itself and may not have anything to do with the SOAP
implementation. I'd suggest creating a main() function in the service
class and running it locally (by itself) to see if you still get the
null pointer exception.
Cyrus
O
Hi
I am a newbie to soap and web services and I am getting an
exception that I cannot find the cause to. Is there anyone that can help?
I have tried to build the simplest client and service
possible. When the client invokes a service, the xml that it gets back is a
null pointer except
10 matches
Mail list logo
