With SOAP 2.2, Xerces 1.3.1, Tomcat 3.23, Apache 1.3,
and NTS 4 ... I've worked through all the issues &
have my server responding properly from the browser,
that it only reponds to POST requests. Now when I try
to test my client install on the server itself by
executing locally:
java org.apache.soap.server.ServiceManagerClient
http://localhost:8080/soap/servlet/messagerouter list
where CLASSPATH =
E:\soap-bin-2.2\soap-2_2\lib\soap.jar;E:\Xerces\xerces-1_3_1\xerces.jar;E:\javamail\javamail-1.2\mail.jar;E:\jaf-1.0.1\activation.jar;E:\bsf-2_2\lib\bsf.jar;E:\rhino\js.jar
org.apache.soap.server.ServiceManagerClient list
..... and I get this strange error, not mentioned in
the Troubleshooting guide.......
Exception in thread "main" [SOAPException:
faultCode=SOAP-ENV:Client; msg=A
'http://schemas.xmlsoap.org/soap/envelope/:Fault'
element must contain a: 'faultcode' element.;
targetException=java.lang.IllegalArgumentException: A
'http://schemas.xmlsoap.org/soap/envelope/:Fault'
element must contain a: 'faultcode' element.]
at
org.apache.soap.rpc.Call.invoke(Call.java:246)
at
org.apache.soap.server.ServiceManagerClient.invokeMethod(ServiceManagerClient.java:129)
at
org.apache.soap.server.ServiceManagerClient.list(ServiceManagerCl
ient.java:151)
at
org.apache.soap.server.ServiceManagerClient.main(ServiceManagerCl
ient.java:237)
Looks like an SOAP document is being validated against
the schema, and failing because the <Faultcode>
element does not have a <fault> element within it...
I'm running the soap.jar file dated 5/29/01.
Anyone else experienced this? Am I doing something
wrong or is this a bug to cross-list to the dev group?
Thanks,
Vikram
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
