I am trying to get a simple zero dependency client to work with Tomcat Axis, but I keep getting response code 500 server error. I'd appreciate any thought about how to debug this. It will work if I point it to some of the xmethods services like:
http://services.xmethods.net:80/soap/servlet/rpcrouter <http://services.xmethods.net/soap/servlet/rpcrouter> but not my home grown (following an example from: http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html?page=1) test web service located at http://localhost:8080/axis/services/fibonacci I have also build a simple stub client using Apache dependencies that access the Fibonacci client, so I know that my homegrown webservice works. However, I'm utterly confused as to why my zero dependency client doesn't work. Well I shouldn't say my client since I took from an example article http://www-128.ibm.com/developerworks/xml/library/x-soapcl/ listing 1 has the source code http://www-128.ibm.com/developerworks/xml/library/x-soapcl/listing1.html The error I get follows (note I renamed the file LowClient.java): Exception in thread "main" java.io.IOException: Server returned HTTP response code: 500 for URL: http://localhost:8080/axis/services/fibonacci at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnec tion.java:800) at LowClient.main(LowClient.java:71) The SOAP message file that LowClient is sending follows: <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <ns1:calculateFibonacci soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:fibonacci"> <in0 href="#id0"/> </ns1:calculateFibonacci> <multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="xsd:int" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">10</multiRef> </soapenv:Body> </soapenv:Envelope> Thanks in advance for helping me understand this Tomcat Client interaction problem.
