Loading ...
Sorry, an error occurred while loading the content.

New Round 2 endpoint - kSOAP

Expand Messages
  • Bob Cunnings
    Hello, The kSOAP endpoint is available for Round 2 base group interop testing at: http://kissen.cs.uni-dortmund.de:8008/ The Round 2 endpoint table has been
    Message 1 of 6 , Nov 8, 2001
    • 0 Attachment
      Hello,

      The kSOAP endpoint is available for Round 2 "base" group interop testing at:

      http://kissen.cs.uni-dortmund.de:8008/

      The Round 2 endpoint table has been updated. Testing with the WM client results in some trouble with empty values being returned... I wonder if "xsi:type" is expected in the request messages?

      Anyway, the kSOAP endpoint is ready for testing!

      RC
    • Alan Kent
      ... Nulls failed: I sent: (xsi is the 2001 schema) I got: Arrays of
      Message 2 of 6 , Nov 8, 2001
      • 0 Attachment
        On Thu, Nov 08, 2001 at 07:03:24PM -0700, Bob Cunnings wrote:
        > Hello,
        >
        > The kSOAP endpoint is available for Round 2 "base" group interop testing at:
        >
        > http://kissen.cs.uni-dortmund.de:8008/

        Nulls failed:
        I sent: <inputString xsi:nil="true"/></m:echoString> (xsi is the 2001 schema)
        I got: <return xsi:type="xsd:string"></return>

        Arrays of integers containing nulls failed too, probably for same reason.

        Unicode chars were echoed as '?' (this may be a 'feature', although
        the HTTP request/response content types both claimed UTF-8 support).

        Carriage returns are interesting. I am not sure who is at fault.
        The XML parser I am using seems to be turning ^M's into newline
        chars during parsing. I think you need to return to be safe.
        I sent:
        <inputString xsi:type="xsd:string"> ab c
        de </inputString>
        I got:
        <return xsi:type="xsd:string">^Mab^Mc
        de^M</return>

        Alan
      • Simon Fell
        ... Looks pretty good, only a couple of failures serialization order test failed [also the faultCode should be a QName, not just Server] request
        Message 3 of 6 , Nov 8, 2001
        • 0 Attachment
          On Thu, 8 Nov 2001 19:03:24 -0700, in soap you wrote:

          >Hello,
          >
          >The kSOAP endpoint is available for Round 2 "base" group interop testing at:
          >
          >http://kissen.cs.uni-dortmund.de:8008/

          Looks pretty good, only a couple of failures

          serialization order test failed [also the faultCode should be a QName,
          not just Server]
          request
          <S:Envelope
          S:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'
          xmlns:S='http://schemas.xmlsoap.org/soap/envelope/'
          xmlns:E='http://schemas.xmlsoap.org/soap/encoding/'
          xmlns:a='http://soapinterop.org/'>
          <S:Body><E:string E:root='0' id='bar'>hello
          world!</E:string><a:echoString><inputString href='#bar'
          /></a:echoString>
          </S:Body></S:Envelope>

          response
          <SOAP-ENV:Envelope
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xmlns:xsd="http://www.w3.org/2001/XMLSchema"
          xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
          xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
          <SOAP-ENV:Body>
          <SOAP-ENV:Fault>
          <faultcode>Server</faultcode>
          <faultstring>java.lang.ClassCastException:
          org.ksoap.SoapPrimitive</faultstring>
          <detail />
          </SOAP-ENV:Fault>
          </SOAP-ENV:Body>
          </SOAP-ENV:Envelope>


          mustUnderstand=1 header test failed
          request
          <S:Envelope
          S:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'
          xmlns:S='http://schemas.xmlsoap.org/soap/envelope/'
          xmlns:E='http://schemas.xmlsoap.org/soap/encoding/'
          xmlns:a='http://soapinterop.org/headers/'
          xmlns:b='http://www.w3.org/2001/XMLSchema-instance'
          xmlns:c='http://www.w3.org/2001/XMLSchema'
          xmlns:d='http://soapinterop.org/'>
          <S:Header>
          <a:Transsaction S:mustUnderstand='1'
          b:type='c:short'>5</a:Transsaction>
          </S:Header>
          <S:Body><d:echoString><inputString b:type='c:string'>Opps, should
          never see me</inputString>
          </d:echoString>
          </S:Body></S:Envelope>

          response [should of faulted]
          <SOAP-ENV:Envelope xmlns:n1="http://soapinterop.org/"
          xmlns:n0="http://soapinterop.org/xsd"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xmlns:xsd="http://www.w3.org/2001/XMLSchema"
          xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
          xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
          <SOAP-ENV:Body
          SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
          <n1:echoStringResponse id="o0" SOAP-ENC:root="1">
          <return xsi:type="xsd:string">Opps, should never see me</return>
          </n1:echoStringResponse>
          </SOAP-ENV:Body>
          </SOAP-ENV:Envelope>

          Cheers
          Simon
        • NAKAMURA, Hiroshi
          Hi, Sorry for responding Simon s article. I ve lost the original article... ... SOAP4R client - kSOAP server: 35/49
          Message 4 of 6 , Nov 8, 2001
          • 0 Attachment
            Hi,

            Sorry for responding Simon's article. I've lost the original article...

            > From: Simon Fell [mailto:soap@...]
            > Sent: Friday, November 09, 2001 3:34 PM

            > On Thu, 8 Nov 2001 19:03:24 -0700, in soap you wrote:
            >
            > >Hello,
            > >
            > >The kSOAP endpoint is available for Round 2 "base" group interop testing at:
            > >
            > >http://kissen.cs.uni-dortmund.de:8008/

            SOAP4R client - kSOAP server: 35/49
            http://www.jin.gr.jp/~nahi/Ruby/SOAP4R/wiki.cgi?cmd=view;name=InteropResults%3A%3ASOAP4R%2F1.3.8-kSOAP+0.8

            Hope this helps,
            // NaHi
          • Stefan Haustein
            ... I hope this is fixed now. ... This should also be fixed now, at least for the server.... Best, Stefan -- Stefan Haustein Univ. Dortmund, FB 4, LS 8 tel:
            Message 5 of 6 , Nov 9, 2001
            • 0 Attachment
              Alan Kent wrote:
              >
              > On Thu, Nov 08, 2001 at 07:03:24PM -0700, Bob Cunnings wrote:
              > > The kSOAP endpoint is available for Round 2 "base" group interop testing at:
              > > http://kissen.cs.uni-dortmund.de:8008/
              >
              > Nulls failed:
              > I sent: <inputString xsi:nil="true"/></m:echoString> (xsi is the 2001 schema)
              > I got: <return xsi:type="xsd:string"></return>

              I hope this is fixed now.

              > Unicode chars were echoed as '?' (this may be a 'feature', although
              > the HTTP request/response content types both claimed UTF-8 support).

              This should also be fixed now, at least for the server....

              Best,
              Stefan


              --
              Stefan Haustein
              Univ. Dortmund, FB 4, LS 8 tel: +49 231 755 2499
              Baroper Str. 301 fax: +49 231 755 5105
              D-44221 Dortmund (Germany) www-ai.cs.uni-dortmund.de
            • Alan Kent
              ... Yes, both seem to be working now. Alan
              Message 6 of 6 , Nov 11, 2001
              • 0 Attachment
                On Sat, Nov 10, 2001 at 12:13:55AM +0100, Stefan Haustein wrote:
                > > Nulls failed:
                > > I sent: <inputString xsi:nil="true"/></m:echoString> (xsi is the 2001 schema)
                > > I got: <return xsi:type="xsd:string"></return>
                >
                > I hope this is fixed now.
                >
                > > Unicode chars were echoed as '?' (this may be a 'feature', although
                > > the HTTP request/response content types both claimed UTF-8 support).
                >
                > This should also be fixed now, at least for the server....

                Yes, both seem to be working now.
                Alan
              Your message has been successfully submitted and would be delivered to recipients shortly.