SoapBuilders Interop testing Group D Results for PocketSOAP

Run at : 07/19/2002 8:33:49 PM
 ASP.NETAxisBEAMSTK3OpenlinkSpraySQLDataSunSystinetWhiteMesa
compound14 / 4
no build
0 / 4
1 2 3 4 
4 / 4
2 / 4
5 6 
4 / 4
4 / 4
4 / 4
4 / 4
4 / 4
compound22 / 2
no build
no build
2 / 2
2 / 2
2 / 2
2 / 2
2 / 2
2 / 2
2 / 2
import13 / 3
3 / 3
no build
3 / 3
3 / 3
3 / 3
3 / 3
3 / 3
3 / 3
3 / 3
import22 / 3
7 
3 / 3
no build
3 / 3
3 / 3
3 / 3
3 / 3
3 / 3
3 / 3
3 / 3
import35 / 6
8 
6 / 6
0 / 6
9 10 11 12 13 14 
6 / 6
6 / 6
6 / 6
6 / 6
6 / 6
6 / 6
6 / 6
interopDocLit8 / 9
15 
no build
no build
9 / 9
8 / 9
16 
9 / 9
9 / 9
8 / 9
17 
9 / 9
9 / 9
InteropdocLitParams8 / 9
18 
no build
no build
9 / 9
8 / 9
19 
9 / 9
9 / 9
9 / 9
9 / 9
9 / 9
interopRpcEnc9 / 9
no build
no build
0 / 9
20 21 22 23 24 25 26 27 28 
8 / 9
29 
9 / 9
9 / 9
9 / 9
9 / 9
9 / 9


1. FAILED: exception: Unexpected HTTP Status code of 404 (expecting 200, 30x, 401, 407 or 500)
2. FAILED: exception: Unexpected HTTP Status code of 404 (expecting 200, 30x, 401, 407 or 500)
3. FAILED: exception: Unexpected HTTP Status code of 404 (expecting 200, 30x, 401, 407 or 500)
4. FAILED: exception: Unexpected HTTP Status code of 404 (expecting 200, 30x, 401, 407 or 500)
5. FAILED: exception: Type mismatch
6. FAILED: exception: Type mismatch
7. FAILED: exception: Client : Server was unable to read request. --> There is an error in XML document (12, 2). --> 'Element' is an invalid node type. Line 12, position 2. at SoapInterop_DN.proxyClass.echoStruct(SOAPStruct inputStruct) at testBase.test(String url, String testName, String str, Int32 i, Single f) in C:\soap_src\SimonFell\wsdl\interop_r3_d\import2\tests.cs:line 45
8. FAILED: exception: Client : Server was unable to read request. --> There is an error in XML document (12, 2). --> 'Element' is an invalid node type. Line 12, position 2.
9. FAILED: exception: Unexpected HTTP Status code of 404 (expecting 200, 30x, 401, 407 or 500)
10. FAILED: exception: Unexpected HTTP Status code of 404 (expecting 200, 30x, 401, 407 or 500)
11. FAILED: exception: Unexpected HTTP Status code of 404 (expecting 200, 30x, 401, 407 or 500)
12. FAILED: exception: Unexpected HTTP Status code of 404 (expecting 200, 30x, 401, 407 or 500)
13. FAILED: exception: Unexpected HTTP Status code of 404 (expecting 200, 30x, 401, 407 or 500)
14. FAILED: exception: Unexpected HTTP Status code of 404 (expecting 200, 30x, 401, 407 or 500)
15. FAILED: exception: Client : The request element <Body xmlns='http://schemas.xmlsoap.org/soap/envelope/'> was not recognized.
16. FAILED: exception: Client : [Virtuoso SOAP server] There is no such procedure
17. FAILED: exception: Client : Missing body information
18. FAILED: exception: Client : The request element <echoVoid xmlns='http://soapinterop.org/xsd'> was not recognized.
19. FAILED: exception: Client : [Virtuoso SOAP server] There is no such procedure
20. FAILED: exception: Server : WSDLReader:The operation requested in the Soap message with soapAction isn't defined in the WSDL file. This may be because it is in the wrong namespace or has incorrect case
21. FAILED: exception: Server : WSDLReader:The operation requested in the Soap message with soapAction isn't defined in the WSDL file. This may be because it is in the wrong namespace or has incorrect case
22. FAILED: exception: Server : WSDLReader:The operation requested in the Soap message with soapAction isn't defined in the WSDL file. This may be because it is in the wrong namespace or has incorrect case
23. FAILED: exception: Server : WSDLReader:The operation requested in the Soap message with soapAction isn't defined in the WSDL file. This may be because it is in the wrong namespace or has incorrect case
24. FAILED: exception: Server : WSDLReader:The operation requested in the Soap message with soapAction isn't defined in the WSDL file. This may be because it is in the wrong namespace or has incorrect case
25. FAILED: exception: Server : WSDLReader:The operation requested in the Soap message with soapAction isn't defined in the WSDL file. This may be because it is in the wrong namespace or has incorrect case
26. FAILED: exception: Server : WSDLReader:The operation requested in the Soap message with soapAction isn't defined in the WSDL file. This may be because it is in the wrong namespace or has incorrect case
27. FAILED: exception: Server : WSDLReader:The operation requested in the Soap message with soapAction isn't defined in the WSDL file. This may be because it is in the wrong namespace or has incorrect case
28. FAILED: exception: Server : WSDLReader:The operation requested in the Soap message with soapAction isn't defined in the WSDL file. This may be because it is in the wrong namespace or has incorrect case
29. FAILED: exception: Client : [Virtuoso SOAP server] There is no such procedure