Sun Java Solaris Communities My SDN Account Join SDN
 
Round 3

Test Results

 

 

Round 3 / Group D

  emptysa import1 import2 import3 compound1 compound2 doclit doclitparam rpcencoded
White Mesa PASS PASS PASS PASS PASS PASS PASS PASS PASS
MS STK v3.0 PASS PASS PASS PASS PASS PASS PASS PASS PASS
IONA 18 18 18 18 18 18 18 18 18
Spray PASS PASS FAIL FAIL PASS PASS FAIL PASS FAIL
ASP.NET PASS PASS PASS FAIL PASS PASS PASS PASS PASS
BEA PASS PASS PASS PASS FAIL FAIL FAIL PASS PASS
Axis 7 7 7 7 7 7 7 7 7
Systinet PASS PASS PASS PASS PASS PASS PASS PASS FAIL
Sun Microsystems PASS PASS PASS PASS PASS PASS PASS PASS PASS
OpenLink PASS PASS FAIL FAIL FAIL PASS FAIL FAIL FAIL
Oracle N/A N/A N/A N/A PASS PASS FAIL FAIL N/A

Round 3 / Group E

  doclit rpcencoded InteropTestList
Whitemesa PASS PASS 18
MS STK v3.0 N/A N/A PASS
Spray N/A N/A FAIL
ASP.NET N/A N/A PASS
BEA N/A N/A PASS
Sun Microsystems PASS PASS PASS
OpenLink N/A N/A PASS

Round 3 / Group F

  Headers
Spray PASS
ASP.NET FAIL
Whitemesa PASS
SQL Data FAIL
BEA FAIL
OpenLink FAIL
Sun Microsystems PASS


Issues :    

  1. nillable="true" added for all the elements in the sequence of SOAPStruct (thereby violating the "Base" Test Specification). Thus, instead of getting mapped to a primitive integer, it gets mapped to a boxed integer type. 

  2. SOAPStruct needs to be xsd:all (as in test specification) instead of xsd:sequence (as in Spray's WSDL).

  3. Service defines a port Import3HttpGet with the binding tns:Import3HttpGet. This binding is not defined in the WSDL document and thus WSDL cannot be imported by the toolkit.

  4. The response message has unqualified child elements where as the WSDL has elementFormDefault="qualified". 
    Here are the  SOAP messages:

    Request :
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 519
    SOAPAction: ""
    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://soapinterop.org/xsd" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><env:Body><ns0:x_Person env:encodingStyle="" Name="Duke" Male="true"><ns0:Age>47.45</ns0:Age><ns0:ID>826.47</ns0:ID></ns0:x_Person></env:Body></env:Envelope>

    Response :
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 519
    SOAPAction: ""
    <env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><env:Header></env:Header><env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><ns100:result_Person xsi:type="ns101:Person" xmlns:ns101="http://soapinterop.org/xsd" xmlns:ns100="http://soapinterop.org/xsd" Male="true" Name="Duke"><Age xsi:type="xsd:double">47.45</Age><ID xsi:type="xsd:float">826.47</ID></ns100:result_Person></env:Body></env:Envelope>

  5. The response message has unqualified child elements where as the WSDL has elementFormDefault="qualified". 
    Here are the SOAP messages :

    Request
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 672
    SOAPAction: ""
    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://soapinterop.org/employee" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><env:Body><ns0:x_Employee env:encodingStyle=""><ns0:person><ans1:Name xmlns:ans1="http://soapinterop.org/person">Duke</ans1:Name><ans1:Male xmlns:ans1="http://soapinterop.org/person">true</ans1:Male></ns0:person><ns0:salary>47.45</ns0:salary><ns0:ID>739</ns0:ID></ns0:x_Employee></env:Body></env:Envelope>

    Response
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 672
    SOAPAction: ""
    <env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><env:Header></env:Header><env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><ns100:result_Employee xsi:type="ns101:Employee" xmlns:ns101="http://soapinterop.org/employee" xmlns:ns100="http://soapinterop.org/employee"><person xsi:type="ns102:Person" xmlns:ns102="http://soapinterop.org/person"><Name xsi:type="xsd:string">Duke</Name><Male xsi:type="xsd:boolean">true</Male></person><salary xsi:type="xsd:double">47.45</salary><ID xsi:type="xsd:int">739</ID></ns100:result_Employee></env:Body></env:Envelope>

  6. The response message has unqualified child elements where as the WSDL has elementFormDefault="qualified". 
    Here are the SOAP messages :

    Request
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 567
    SOAPAction: ""
    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://soapinterop.org/xsd" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><env:Body><ns0:echoStructParam env:encodingStyle=""><ns0:varFloat>672.91</ns0:varFloat><ns0:varInt>346</ns0:varInt><ns0:varString>Hello Duke!</ns0:varString></ns0:echoStructParam></env:Body></env:Envelope>

    Response
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 567
    SOAPAction: ""
    <env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><env:Header></env:Header><env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><ns100:echoStructReturn xsi:type="ns101:SOAPStruct" xmlns:ns101="http://soapinterop.org/xsd" xmlns:ns100="http://soapinterop.org/xsd"><varFloat xsi:type="xsd:float">672.91</varFloat><varInt xsi:type="xsd:int">346</varInt><varString xsi:type="xsd:string">Hello Duke!</varString></ns100:echoStructReturn></env:Body></env:Envelope>

  7. Endpoint is down.

  8. Received a Null Pointer Exception from the server for echoStringArray.  
    Here are the SOAP messages :

    Request
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 1162
    SOAPAction: ""
    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding
    /" xmlns:ns0="http://soapinterop.org/WSDLInteropTestRpcEnc" xmlns:ns1="http://soapinterop.org/xsd" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><env:Body><ns0:echoStringArray><param0 href="#ID1"/>
    </ns0:echoStringArray><ns1:ArrayOfstring id="ID1" xsi:type="enc:Array" enc:arrayType="xsd:string[14]"><itemxsi:type="xsd:string">Now</item><item xsi:type="xsd:string">is</item>
    <item xsi:type="xsd:string">the</item><itemxsi:type="xsd:string">time</item><item xsi:type="xsd:string">for</item>
    <item xsi:type="xsd:string">all</item><item xsi:type="xsd:string">wise</item><item xsi:type="xsd:string">men</item><itemxsi:type="xsd:string">to</item><itemxsi:type="xsd:string">raise</item><item xsi:type="xsd:string">for</item><item xsi:type="xsd:string">
    the</item><item xsi:type="xsd:string">country's</item><item xsi:type="xsd:string">help</item></ns1:ArrayOfstring></env:Body></env:Envelope>

    Response
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 1162
    SOAPAction: ""
    <?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body>
    <ns0:Fault xmlns:ns0="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>ns0:Server</faultcode><faultstring>
    An exception occurred: java.lang.NullPointerException</faultstring><detail xmlns:ijm="urn:idoox-java-mapping">
    <ijm:idoox-java-mapping.java.lang.NullPointerException><ijm:stack-trace>java.lang.NullPointerException
    at com.idoox.wasp.serialization.wsdl.SchemaHandler.findNextInAll(SchemaHandler.java:401)
    at com.idoox.wasp.serialization.wsdl.SchemaHandler.nextSchemaConstruct(SchemaHandler.java:310)
    at com.idoox.wasp.serialization.wsdl.WSDLDeserializationContext.nextSchemaConstruct(WSDLDeserializationContext.java:525)
    at com.idoox.wasp.serialization.SerializationHelper.deserialize(SerializationHelper.java:351)
    at com.idoox.wasp.serialization.SerializationHelper.deserialize(SerializationHelper.java:179)
    at com.idoox.wasp.serialization.ReflectionDeserializer.processArray(ReflectionDeserializer.java:356)
    at com.idoox.wasp.serialization.ReflectionDeserializer.deserialize(ReflectionDeserializer.java:127)
    at com.idoox.wasp.serialization.BasicConstructDeserializer.deserialize(BasicConstructDeserializer.java:15
    4)
    at com.idoox.wasp.serialization.xml.XMLEncDeserializerWrapper.deserialize(XMLEncDeserializerWrapper.java:
    47)
    at com.idoox.wasp.serialization.SerializationHelper.deserializeElement(SerializationHelper.java:295)
    at com.idoox.wasp.serialization.WaspSerializationHelper.deserialize(WaspSerializationHelper.java:150)
    at com.idoox.wasp.server.adaptor.JavaAdaptorInvoker.deserializeOneReference(JavaAdaptorInvoker.java:1145)
    at com.idoox.wasp.server.adaptor.JavaAdaptorInvoker.deserializeReferences(JavaAdaptorInvoker.java:1077)
    at com.idoox.wasp.server.adaptor.JavaAdaptorInvoker.rpcReadServiceEnd(JavaAdaptorInvoker.java:430)
    at com.idoox.wasp.server.adaptor.JavaAdaptorInvoker.invoke(JavaAdaptorInvoker.java:352)
    at com.idoox.wasp.server.adaptor.JavaAdaptorImpl.dispatch(JavaAdaptorImpl.java:134)
    at com.idoox.wasp.server.AdaptorTemplate.doDispatch(AdaptorTemplate.java:193)
    at com.idoox.wasp.server.AdaptorTemplate.dispatch(AdaptorTemplate.java:167)
    at com.idoox.wasp.server.ServiceConnector.dispatch(ServiceConnector.java:294)
    at com.idoox.wasp.server.ServiceManager.dispatch(ServiceManager.java:345)
    at com.idoox.wasp.server.ServiceManager$DispatcherConnHandler.handlePost(ServiceManager.java:1899)
    at com.idoox.transport.http.server.Jetty$WaspHttpHandler.handle(Jetty.java:97)
    at com.mortbay.HTTP.HandlerContext.handle(HandlerContext.java:1087)
    at com.mortbay.HTTP.HttpServer.service(HttpServer.java:675)
    at com.mortbay.HTTP.HttpConnection.service(HttpConnection.java:457)
    at com.mortbay.HTTP.HttpConnection.handle(HttpConnection.java:317)
    at com.mortbay.HTTP.SocketListener.handleConnection(SocketListener.java:99)
    at com.mortbay.Util.ThreadedServer.handle(ThreadedServer.java:254)
    at com.mortbay.Util.ThreadPool$PoolThreadRunnable.run(ThreadPool.java:601)
    at java.lang.Thread.run(Thread.java:484)
    </ijm:stack-trace></ijm:idoox-java-mapping.java.lang.NullPointerException></detail></ns0:Fault>
    </SOAP-ENV:Body></SOAP-ENV:Envelope>

  9. The WSDL published is different from the Standard Specification WSDL in that there is an additional namespace attribute to the <soap:body> elements in the soap:binding.  Since its a Doc/Lit WSDL, the namespace attribute doesn't really apply here, according to the WSDL specification. This could be the problem.
    The Server returned a SOAP:Fault

    Request
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 465
    SOAPAction: "http://soapinterop.org/"
    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://soapinterop.org/xsd" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><env:Body>
    <ns0:echoStringParam env:encodingStyle="">foo</ns0:echoStringParam></env:Body></env:Envelope>

    Response
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 465
    SOAPAction: "http://soapinterop.org/"
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><SOAP:Body><SOAP:Fault><faultcode>SOAP:Client</faultcode><faultstring>
    [Virtuoso SOAP server] There is no such procedure</faultstring><detail /></SOAP:Fault></SOAP:Body></SOAP:Envelope>

  10. The WSDL published is different from the Standard Specification WSDL in that there is an additional namespace attribute to the <soap:body> elements in the soap:binding.  Since its a Doc/Lit WSDL, the namespace attribute doesn't really apply here, according to the WSDL specification. This could be the problem.
    The Server returned a SOAP:Fault

    Request
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 472
    SOAPAction: "http://soapinterop.org/"
    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://soapinterop.org/xsd" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><env:Body>
    <ns0:echoString env:encodingStyle=""><param0>foo</param0></ns0:echoString></env:Body></env:Envelope>

    Response
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 472
    SOAPAction: "http://soapinterop.org/"
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><SOAP:Body><SOAP:Fault><faultcode>SOAP:Server</faultcode><faultstring>
    [Virtuoso SOAP server] Not enough actual parameters in a SOAP request</faultstring><detail/></SOAP:Fault></SOAP:Body></SOAP:Envelope>

  11. Sending an empty SOAP body is rejected by the server. Here are the SOAP messages :
    Request
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 390
    SOAPAction: "http://soapinterop.org/"
    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://soapinterop.org/xsd" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><env:Body/></env:Envelope>

    Response
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 390
    SOAPAction: "http://soapinterop.org/"
    <?xml version='1.0' encoding='UTF-8'?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <SOAP-ENV:Body>
    <SOAP-ENV:Fault>
    <faultcode>SOAP-ENV:Server</faultcode>
    <faultstring>Body entries cannot be empty!</faultstring>
    <faultactor>/soapbuilder/r3/InteropTestDocLit</faultactor>
    </SOAP-ENV:Fault>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>

  12. The SOAP response contains an empty body, as opposed without a wrapper (echoVoidResponse), as stipulated by the WSDL. 
    Here are the SOAP messages "
    Request
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 436
    SOAPAction: "http://soapinterop.org/"
    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/
    xmlns:ns0="http://soapinterop.org/xsd" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><env:Body>
    <ns0:echoVoid env:encodingStyle=""/></env:Body></env:Envelope>

    Response
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 436
    SOAPAction: "http://soapinterop.org/"
    <?xml version='1.0' encoding='UTF-8'?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <SOAP-ENV:Body>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>

  13. ComplexType List in the WSDL is modified from that of the Standard WSDL by making "nillable=true".  This deviation causes -
    "unexpected element type: expected={http://www.w3.org/2001/XMLSchema}int, actual={http://www.w3.org/2001/XMLSchema}integer"
    Here are the SOAP messages :
    Request
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 891
    SOAPAction: ""
    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding
    /" xmlns:ns0="http://soapinterop.org/WSDLInteropTestRpcEnc" xmlns:ns1="http://soapinterop.org/xsd" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><env:Body><ns0:echoLinkedList><param0 href="#ID1"/>
    </ns0:echoLinkedList><ns1:List id="ID1" xsi:type="ns1:List"><varInt xsi:type="xsd:int">23532</varInt><varString xsi:type="xsd:string">Hello SOAPBuilders!</varString><child href="#ID2"/></ns1:List><ns1:List id="ID2" 
    xsi:type="ns1:List"><varInt xsi:type="xsd:int">-25434</varInt><varString xsi:type="xsd:string">Hey SOAPBuilders!
    </varString><child xsi:type="xsd:anyType" xsi:nil="1"/></ns1:List></env:Body></env:Envelope>

    Response
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 891
    SOAPAction: ""
    <?xml version="1.0"?><SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/
    xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
    xmlns:ns1="http://soapinterop.org/xsd" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><m:echoLinkedListResponse SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:m="http://soapinterop.org/
    WSDLInteropTestRpcEnc"><return xsi:type="ns1:List"><varInt xsi:type="xsd:int">23532</varInt><varString xsi:type="xsd:string">Hello SOAPBuilders!</varString><child xsi:type="ns1:List"><varInt xsi:type="xsd:integer">-25434</varInt><varString xsi:type="xsd:string">Hey SOAPBuilders!</varString><child xsi:nil="true"/></child></return></m:echoLinkedListResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>

  14. Service defines a port InteropTestHeadersHttpGet with the binding tns:InteropTestHeadersHttpGet. This binding is not defined in the WSDL document and thus WSDL can not be imported by the toolkit.
    modeler error: invalid entity name: "InteropTestHeadersHttpGet" (in namespace: "http://soapinterop.org")

  15. The header information is carried inside the body of the SOAP response. Here are the SOAP messages:
    Request
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 723
    SOAPAction: "http://soapinterop.org/"
    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://soapinterop.org/xsd" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><env:Header><ns0:Header1 env:encodingStyle=""><ns0:string>Hello SOAPBuilders!</ns0:string><ns0:int>23532</ns0:int>
    </ns0:Header1><ns0:Header2 env:encodingStyle=""><ns0:int>-25434</ns0:int><ns0:string>Hey SOAPBuilders!</ns0:string></ns0:Header2></env:Header><env:Body><ns0:echoStringParam env:encodingStyle="">foo</ns0:echoStringParam></env:Body></env:Envelope>

    Response
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 723
    SOAPAction: "http://soapinterop.org/"
    <?xml version="1.0" encoding="UTF-8" standalone="no"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://soapinterop.org/" xmlns:types="http://soapinterop.org/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001
    /XMLSchema" >
    <SOAP-ENV:Body><types:echoStringReturn xmlns:types="http://soapinterop.org/xsd">Header1(Hello SOAPBuilders!,
    23532)Header2(-25434, Hey SOAPBuilders!)
    foo</types:echoStringReturn></SOAP-ENV:Body></SOAP-ENV:Envelope>

  16. The WSDL published is different from the Standard Specification WSDL in that there is an additional namespace attribute to the <soap:body> elements in the soap:binding.  Since its a Doc/Lit WSDL, the namespace attribute doesn't really apply here, according to the WSDL specification.
    The server is returning a SOAP fault.  Here are the SOAP messages :
    Request
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 723
    SOAPAction: ""
    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://soapinterop.org/xsd" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><env:Header><ns0:Header1 env:encodingStyle=""><ns0:string>Hello SOAPBuilders!</ns0:string><ns0:int>23532</ns0:int>
    </ns0:Header1><ns0:Header2 env:encodingStyle=""><ns0:int>-25434</ns0:int><ns0:string>Hey SOAPBuilders!</ns0:string></ns0:Header2></env:Header><env:Body><ns0:echoStringParam env:encodingStyle="">foo</ns0:echoStringParam></env:Body></env:Envelope>

    Response
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 723
    SOAPAction: ""
    <env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><env:Header></env:Header><env:Body><env:Fault><faultcode>Server</faultcode><faultstring>argument typemismatch</faultstring><detail><bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webserv
    ice/fault/1.0.0">java.lang.IllegalArgumentException: argument type mismatch at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.webservice.component.javaclass.JavaClassInvocationHandler.invoke(JavaClassInvocationHandler.j
    ava:84)
    at weblogic.webservice.core.handler.InvokeHandler.handleRequest(InvokeHandler.java:78)
    at weblogic.webservice.core.HandlerChain.handleRequest(HandlerChain.java:131)
    at weblogic.webservice.core.DefaultOperation.process(DefaultOperation.java:539)
    at weblogic.webservice.core.DefaultWebService.invoke(DefaultWebService.java:264)
    at weblogic.webservice.server.servlet.ServletBase.serverSideInvoke(ServletBase.java:362)
    at weblogic.webservice.server.servlet.WebServiceServlet.serverSideInvoke(WebServiceServlet.java:269)
    at weblogic.webservice.server.servlet.ServletBase.doPost(ServletBase.java:346)
    at weblogic.webservice.server.servlet.WebServiceServlet.doPost(WebServiceServlet.java:237)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5
    412)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    </bea_fault:stacktrace></detail></env:Fault></env:Body>
    </env:Envelope>

  17. The WSDL published is different from the Standard Specification WSDL in that there is an additional namespace attribute to the <soap:body> elements in the soap:binding.  Since its a Doc/Lit WSDL, the namespace attribute doesn't really apply here, according to the WSDL specification.
    The server is returning a SOAP fault.  Here are the SOAP messages :
    Request
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 723
    SOAPAction: "http://soapinterop.org/"
    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/
    xmlns:ns0="http://soapinterop.org/xsd" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><env:Header>
    <ns0:Header1 env:encodingStyle=""><ns0:string>Hello SOAPBuilders!</ns0:string><ns0:int>23532</ns0:int></ns0:Header1>
    <ns0:Header2 env:encodingStyle=""><ns0:int>-25434</ns0:int><ns0:string>Hey SOAPBuilders!</ns0:string></ns0:Header2>
    </env:Header><env:Body><ns0:echoStringParam env:encodingStyle="">foo</ns0:echoStringParam></env:Body></env:Envelope>

    Response
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 723
    SOAPAction: "http://soapinterop.org/"
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><SOAP:Body><SOAP:Fault><faultcode>
    SOAP:Client</faultcode><faultstring>[Virtuoso SOAP server] There is no such procedure</faultstring><detail /></SOAP:Fault>
    </SOAP:Body></SOAP:Envelope>

  18. Network problem/cannot connect

Results Updated: Oct 2, 2002 2:20 PM

For more information, please contact web master.

Related Links