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

Re: [soapbuilders] mssoapinterop.org updated

Expand Messages
  • Bob Cunnings
    Paul, Here is the request for echoStructAsSimpleTypes :
    Message 1 of 22 , Aug 2, 2001
    • 0 Attachment
      Paul,

      Here is the request for "echoStructAsSimpleTypes":

      <?xml version="1.0" encoding="UTF-8"?>
      <SOAP-ENV:Envelope xmlns:SOAP-
      ENV="http://schemas.xmlsoap.org/soap/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" SOAP-
      ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
      >
      <SOAP-ENV:Body>
      <m:echoStructAsSimpleTypes xmlns:m="http://soapinterop.org/">
      <inputStruct>
      <varInt>42</varInt>
      <varFloat>.006</varFloat>
      <varString>foo</varString>
      </inputStruct>
      </m:echoStructAsSimpleTypes>
      </SOAP-ENV:Body>
      </SOAP-ENV:Envelope>

      Here is the response:

      <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
      xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
      xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
      xmlns:xsd="http://www.w3.org/1999/XMLSchema" SOAP-
      ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
      xmlns:SOAP-
      ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-
      ENV:Body><namesp1:echoStructAsSimpleTypesResponse
      xmlns:namesp1="http://soapinterop.org/"><outputString
      xsi:type="xsd:string">foo</outputString><outputInteger
      xsi:type="xsd:int">42</outputInteger><outputFloat
      xsi:type="xsd:float">.006</outputFloat></namesp1:echoStructAsSi
      mpleTypesResponse></SOAP-ENV:Body></SOAP-
      ENV:Envelope>

      Here is the request for "echo string header":

      <?xml version="1.0" encoding="UTF-8"?>
      <SOAP-ENV:Envelope xmlns:SOAP-
      ENV="http://schemas.xmlsoap.org/soap/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" SOAP-
      ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
      >
      <SOAP-ENV:Header>
      <h:echoMeStringRequest
      xmlns:h="http://soapinterop.org/echoheader/" SOAP-
      ENV:actor="http://schemas.xmlsoap.org/soap/actor/next">foo</h:e
      choMeStringRequest>
      </SOAP-ENV:Header>
      <SOAP-ENV:Body>
      <m:echoVoid xmlns:m="http://soapinterop.org/">
      </m:echoVoid>
      </SOAP-ENV:Body>
      </SOAP-ENV:Envelope>

      Here is the response:

      <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
      xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
      xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
      xmlns:xsd="http://www.w3.org/1999/XMLSchema" SOAP-
      ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
      xmlns:SOAP-
      ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-
      ENV:Body><SOAP-ENV:Fault><faultcode
      xsi:type="xsd:string">SOAP-ENV:Client</faultcode><faultstring
      xsi:type="xsd:string">SOAPAction '"http://soapinterop.org/"' shall
      match quoted 'urn:soapinterop'
      </faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-
      ENV:Envelope>

      Thanks,

      RC
      > Hi, Bob!
      >
      > --- Bob Cunnings <cunnings@...> wrote:
      > > Having some trouble there...
      > > Group B: response uses 1999 Schema
      > > Group C: is expecting SOAPAction "urn:soapinterop"
      > > rather than "http://soapinterop.org/"
      > wiredumps? it replies 1999 on 1999 and 2001 on 2001 for me. It also
      > allows both "urn:soapinterop" and "http://soapinterop.org/" as
      > SOAPAction. Could it be something else?
      >
      > Best wishes, Paul.
      >
      > --- Bob Cunnings <cunnings@...> wrote:
      > > Paul,
      > >
      > > Having some trouble there...
      > >
      > > Group B: response uses 1999 Schema
      > >
      > > Group C: is expecting SOAPAction "urn:soapinterop"
      > > rather than "http://soapinterop.org/"
      > >
      > > RC
      > >
      > > > Hi, Bob!
      > > >
      > > > > No, I just updated the WM client results mentioned below to
      > > > > include SOAP:Lite, so you should see them there.
      > > > I see SOAP::Lite only in [1], but not in [2] or [3]. What should
      > > I do
      > > > to be there? :)
      > > >
      > > > > Maybe you can can get a wire dump at your end.
      > > > Should be fixed now.
      > > >
      > > > Best wishes, Paul.
      > > >
      > > > [1] http://www.whitemesa.com/interop/results/results.htm
      > > > [2] http://www.whitemesa.com/interop/results/b/results.htm
      > > > [3] http://www.whitemesa.com/interop/results/c/results.htm
      > > >
      > > > --- Bob Cunnings <cunnings@...> wrote:
      > > > > Paul,
      > > > >
      > > > > No, I just updated the WM client results mentioned below to
      > > > > include SOAP:Lite, so you should see them there.
      > > > >
      > > > > I've had trouble with echoFloatArray on the SOAP:Lite endpoint
      > > all
      > > > > along, but I can' get a wire dump since the same virtual
      > > hosting
      > > > > problem that Sam mentioned prevents me from using tcpTrace.
      > > > > I get 404 from your endpoint since the host header get passed
      > > > > straight through tcpTrace, and it's naming the local host here,
      > > of
      > > > > course.
      > > > >
      > > > > Maybe you can can get a wire dump at your end.
      > > > >
      > > > > RC
      > > > >
      > > > >
      > > > > > Hi, Bob!
      > > > > >
      > > > > > > [1] http://www.whitemesa.com/interop/results/results.htm
      > > > > > There is still some problem with echoFloatArray with
      > > SOAP::Lite,
      > > > > but
      > > > > > I don't see wiredump there.
      > > > > >
      > > > > > Do I need to be regirstered to get into results for Group B
      > > and
      > > > > Group
      > > > > > C? Thank you.
      > > > > >
      > > > > > Best wishes, Paul.
      > > > > >
      > > > > > --- Bob Cunnings <cunnings@...> wrote:
      > > > > > > Hello,
      > > > > > >
      > > > > > > Ran tests with WM client...
      > > > > > >
      > > > > > > "base" methods: echoStruct, echoStructArray faulting for
      > > .NET
      > > > > > > Remoting endpoint [1]
      > > > > > >
      > > > > > > "Group B" : echoNestedStruct, echoNestedArray faulting for
      > > .NET
      > > > >
      > > > > > > Remoting endpoint [2]
      > > > > > >
      > > > > > > "Group C": returned "string" header entry element in wrong
      > > > > > > namespace, headers targeted at "default" actor not
      > > recognized
      > > > > for
      > > > > > > ASP.NET [3]
      > > > > > >
      > > > > > > RC
      > > > > > >
      > > > > > > [1] http://www.whitemesa.com/interop/results/results.htm
      > > > > > > [2] http://www.whitemesa.com/interop/results/b/results.htm
      > > > > > > [3] http://www.whitemesa.com/interop/results/c/results.htm
      > > > > > >
      > > > > > >
      > > > > > > > The .NET Framework runtime has been updated on
      > > > > mssoapinterop.org.
      > > > > > >
      > > > > > > > This update includes fixes, etc. This update is for .NET
      > > > > Remoting
      > > > > > >
      > > > > > > > and ASP.NET Web Services. The SOAP Toolkit runtime has
      > > not
      > > > > been
      > > > > > > > changed.
      > > > > > > >
      > > > > > > > Thanks,
      > > > > > > > Keith
      > > > > > > >
      > > > > > > >
      > > > > > > >
      > > > > > > >
      > > > >
      > > -----------------------------------------------------------------
      > > > > > > > This group is a forum for builders of SOAP
      > > implementations to
      > > > > > > discuss implementation and interoperability issues. Please
      > > > > stay
      > > > > > > on-topic.
      > > > > > > >
      > > > > > > > To unsubscribe from this group, send an email to:
      > > > > > > > soapbuilders-unsubscribe@yahoogroups.com
      > > > > > > >
      > > > > > > >
      > > > > > > >
      > > > > > > > Your use of Yahoo! Groups is subject to
      > > > > > > http://docs.yahoo.com/info/terms/
      > > > > > > >
      > > > > > >
      > > > > > >
      > > > > > >
      > > > > > > ------------------------ Yahoo! Groups Sponsor
      > > > > > >
      > > > > > >
      > > > >
      > > -----------------------------------------------------------------
      > > > > > > This group is a forum for builders of SOAP implementations
      > > to
      > > > > > > discuss implementation and interoperability issues. Please
      > > > > stay
      > > > > > > on-topic.
      > > > > > >
      > > > > > > To unsubscribe from this group, send an email to:
      > > > > > > soapbuilders-unsubscribe@yahoogroups.com
      > > > > > >
      > > > > > >
      > > > > > >
      > > > > > > Your use of Yahoo! Groups is subject to
      > > > > > > http://docs.yahoo.com/info/terms/
      > > > > > >
      > > > > > >
      > > > > >
      > > > > >
      > > > > > __________________________________________________
      > > > > > Do You Yahoo!?
      > > > > > Make international calls for as low as $.04/minute with
      > > Yahoo!
      > > > > Messenger
      > > > > > http://phonecard.yahoo.com/
      > > > > >
      > > > > >
      > > > > >
      > > -----------------------------------------------------------------
      > > > > > This group is a forum for builders of SOAP implementations to
      > > > > discuss implementation and interope
      > > > > rability issues. Please stay on-topic.
      > > > > >
      > > > > > To unsubscribe from this group, send an email to:
      > > > > > soapbuilders-unsubscribe@yahoogroups.com
      > > > > >
      > > > > >
      > > > > >
      > > > > > Your use of Yahoo! Groups is subject to
      > > > > http://docs.yahoo.com/info/terms/
      > > > > >
      > > > >
      > > > >
      > > > >
      > > > > ------------------------ Yahoo! Groups Sponsor
      > > > >
      > > > >
      > > -----------------------------------------------------------------
      > > > > This group is a forum for builders of SOAP implementations to
      > > > > discuss implementation and interoperability issues. Please
      > > stay
      > > > > on-topic.
      > > > >
      > > > > To unsubscribe from this group, send an email to:
      > > > > soapbuilders-unsubscribe@yahoogroups.com
      > > > >
      > > > >
      > > > >
      > > > > Your use of Yahoo! Groups is subject to
      > > > > http://docs.yahoo.com/info/terms/
      > > > >
      > > > >
      > > >
      > > >
      > > > __________________________________________________
      > > > Do You Yahoo!?
      > > > Make international calls for as low as $.04/minute with Yahoo!
      > > Messenger
      > > > http://phonecard.yahoo.com/
      > > >
      > > >
      > >
      > === message truncated ===
      >
      >
      > __________________________________________________
      > Do You Yahoo!?
      > Make international calls for as low as $.04/minute with Yahoo! Messenger
      > http://phonecard.yahoo.com/
      >
      >
      > -----------------------------------------------------------------
      > This group is a forum for builders of SOAP implementations to discuss implementation and interope
      rability issues. Please stay on-topic.
      >
      > To unsubscribe from this group, send an email to:
      > soapbuilders-unsubscribe@yahoogroups.com
      >
      >
      >
      > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
      >
    • Paul Kulchenko
      Hi, Bob! ... That s the same problem as I described in message to Hiroshi. There is not enough information in your request to define whether it s XMLSchema
      Message 2 of 22 , Aug 2, 2001
      • 0 Attachment
        Hi, Bob!

        --- Bob Cunnings <cunnings@...> wrote:
        > Here is the request for "echoStructAsSimpleTypes":
        That's the same problem as I described in message to Hiroshi. There
        is not enough information in your request to define whether it's
        XMLSchema 2001 or 1999. You declare, but never used xsd namespace and
        your message is the same as:

        <?xml version="1.0" encoding="UTF-8"?>
        <SOAP-ENV:Envelope
        xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
        xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
        SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
        <SOAP-ENV:Body>
        <m:echoStructAsSimpleTypes xmlns:m="http://soapinterop.org/">
        <inputStruct>
        <varInt>42</varInt>
        <varFloat>.006</varFloat>
        <varString>foo</varString>
        </inputStruct>
        </m:echoStructAsSimpleTypes>
        </SOAP-ENV:Body>
        </SOAP-ENV:Envelope>

        which doesn't use any XML Schema datatypes. My endpoint uses 1999 by
        default, so it replies with 1999. I may switch to 2001, but it
        doesn't help in general. Any ideas?

        > Here is the request for "echo string header":
        Sorry, my fault, I didn't refresh endpoint. Will accept both
        SOAPActions now. Thank you.

        Best wishes, Paul.

        > <?xml version="1.0" encoding="UTF-8"?>
        > <SOAP-ENV:Envelope xmlns:SOAP-
        > ENV="http://schemas.xmlsoap.org/soap/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" SOAP-
        > ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
        > >
        > <SOAP-ENV:Body>
        > <m:echoStructAsSimpleTypes xmlns:m="http://soapinterop.org/">
        > <inputStruct>
        > <varInt>42</varInt>
        > <varFloat>.006</varFloat>
        > <varString>foo</varString>
        > </inputStruct>
        > </m:echoStructAsSimpleTypes>
        > </SOAP-ENV:Body>
        > </SOAP-ENV:Envelope>
        >
        > Here is the response:
        >
        > <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
        > xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
        > xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
        > xmlns:xsd="http://www.w3.org/1999/XMLSchema" SOAP-
        > ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
        > xmlns:SOAP-
        > ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-
        > ENV:Body><namesp1:echoStructAsSimpleTypesResponse
        > xmlns:namesp1="http://soapinterop.org/"><outputString
        > xsi:type="xsd:string">foo</outputString><outputInteger
        > xsi:type="xsd:int">42</outputInteger><outputFloat
        > xsi:type="xsd:float">.006</outputFloat></namesp1:echoStructAsSi
        > mpleTypesResponse></SOAP-ENV:Body></SOAP-
        > ENV:Envelope>
        >
        > Here is the request for "echo string header":
        >
        > <?xml version="1.0" encoding="UTF-8"?>
        > <SOAP-ENV:Envelope xmlns:SOAP-
        > ENV="http://schemas.xmlsoap.org/soap/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" SOAP-
        > ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
        > >
        > <SOAP-ENV:Header>
        > <h:echoMeStringRequest
        > xmlns:h="http://soapinterop.org/echoheader/" SOAP-
        > ENV:actor="http://schemas.xmlsoap.org/soap/actor/next">foo</h:e
        > choMeStringRequest>
        > </SOAP-ENV:Header>
        > <SOAP-ENV:Body>
        > <m:echoVoid xmlns:m="http://soapinterop.org/">
        > </m:echoVoid>
        > </SOAP-ENV:Body>
        > </SOAP-ENV:Envelope>
        >
        > Here is the response:
        >
        > <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
        > xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
        > xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
        > xmlns:xsd="http://www.w3.org/1999/XMLSchema" SOAP-
        > ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
        > xmlns:SOAP-
        > ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-
        > ENV:Body><SOAP-ENV:Fault><faultcode
        > xsi:type="xsd:string">SOAP-ENV:Client</faultcode><faultstring
        > xsi:type="xsd:string">SOAPAction '"http://soapinterop.org/"' shall
        > match quoted 'urn:soapinterop'
        > </faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-
        > ENV:Envelope>
        >
        > Thanks,
        >
        > RC
        > > Hi, Bob!
        > >
        > > --- Bob Cunnings <cunnings@...> wrote:
        > > > Having some trouble there...
        > > > Group B: response uses 1999 Schema
        > > > Group C: is expecting SOAPAction "urn:soapinterop"
        > > > rather than "http://soapinterop.org/"
        > > wiredumps? it replies 1999 on 1999 and 2001 on 2001 for me. It
        > also
        > > allows both "urn:soapinterop" and "http://soapinterop.org/" as
        > > SOAPAction. Could it be something else?
        > >
        > > Best wishes, Paul.
        > >
        > > --- Bob Cunnings <cunnings@...> wrote:
        > > > Paul,
        > > >
        > > > Having some trouble there...
        > > >
        > > > Group B: response uses 1999 Schema
        > > >
        > > > Group C: is expecting SOAPAction "urn:soapinterop"
        > > > rather than "http://soapinterop.org/"
        > > >
        > > > RC
        > > >
        > > > > Hi, Bob!
        > > > >
        > > > > > No, I just updated the WM client results mentioned below to
        >
        > > > > > include SOAP:Lite, so you should see them there.
        > > > > I see SOAP::Lite only in [1], but not in [2] or [3]. What
        > should
        > > > I do
        > > > > to be there? :)
        > > > >
        > > > > > Maybe you can can get a wire dump at your end.
        > > > > Should be fixed now.
        > > > >
        > > > > Best wishes, Paul.
        > > > >
        > > > > [1] http://www.whitemesa.com/interop/results/results.htm
        > > > > [2] http://www.whitemesa.com/interop/results/b/results.htm
        > > > > [3] http://www.whitemesa.com/interop/results/c/results.htm
        > > > >
        > > > > --- Bob Cunnings <cunnings@...> wrote:
        > > > > > Paul,
        > > > > >
        > > > > > No, I just updated the WM client results mentioned below to
        >
        > > > > > include SOAP:Lite, so you should see them there.
        > > > > >
        > > > > > I've had trouble with echoFloatArray on the SOAP:Lite
        > endpoint
        > > > all
        > > > > > along, but I can' get a wire dump since the same virtual
        > > > hosting
        > > > > > problem that Sam mentioned prevents me from using tcpTrace.
        > > > > > I get 404 from your endpoint since the host header get
        > passed
        > > > > > straight through tcpTrace, and it's naming the local host
        > here,
        > > > of
        > > > > > course.
        > > > > >
        > > > > > Maybe you can can get a wire dump at your end.
        > > > > >
        > > > > > RC
        > > > > >
        > > > > >
        > > > > > > Hi, Bob!
        > > > > > >
        > > > > > > > [1]
        > http://www.whitemesa.com/interop/results/results.htm
        > > > > > > There is still some problem with echoFloatArray with
        > > > SOAP::Lite,
        > > > > > but
        > > > > > > I don't see wiredump there.
        > > > > > >
        > > > > > > Do I need to be regirstered to get into results for Group
        > B
        > > > and
        > > > > > Group
        > > > > > > C? Thank you.
        > > > > > >
        > > > > > > Best wishes, Paul.
        > > > > > >
        > > > > > > --- Bob Cunnings <cunnings@...> wrote:
        > > > > > > > Hello,
        > > > > > > >
        > > > > > > > Ran tests with WM client...
        > > > > > > >
        > > > > > > > "base" methods: echoStruct, echoStructArray faulting
        > for
        > > > .NET
        > > > > > > > Remoting endpoint [1]
        > > > > > > >
        > > > > > > > "Group B" : echoNestedStruct, echoNestedArray faulting
        > for
        > > > .NET
        > > > > >
        > > > > > > > Remoting endpoint [2]
        > > > > > > >
        > > > > > > > "Group C": returned "string" header entry element in
        > wrong
        > > > > > > > namespace, headers targeted at "default" actor not
        > > > recognized
        > > > > > for
        > > > > > > > ASP.NET [3]
        > > > > > > >
        > > > > > > > RC
        > > > > > > >
        > > > > > > > [1]
        > http://www.whitemesa.com/interop/results/results.htm
        > > > > > > > [2]
        > http://www.whitemesa.com/interop/results/b/results.htm
        > > > > > > > [3]
        > http://www.whitemesa.com/interop/results/c/results.htm
        > > > > > > >
        > > > > > > >
        >
        === message truncated ===


        __________________________________________________
        Do You Yahoo!?
        Make international calls for as low as $.04/minute with Yahoo! Messenger
        http://phonecard.yahoo.com/
      • Bob Cunnings
        Paul, Oops, I forgot to enable explicit typing on the client when sending the request! I have been generally doing this, at least for now. I ll try again. RC
        Message 3 of 22 , Aug 2, 2001
        • 0 Attachment
          Paul,

          Oops, I forgot to enable explicit typing on the client when sending
          the request! I have been generally doing this, at least for now.

          I'll try again.

          RC

          > Hi, Bob!
          >
          > --- Bob Cunnings <cunnings@...> wrote:
          > > Here is the request for "echoStructAsSimpleTypes":
          > That's the same problem as I described in message to Hiroshi. There
          > is not enough information in your request to define whether it's
          > XMLSchema 2001 or 1999. You declare, but never used xsd namespace and
          > your message is the same as:
          >
          > <?xml version="1.0" encoding="UTF-8"?>
          > <SOAP-ENV:Envelope
          > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
          > xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
          > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
          > <SOAP-ENV:Body>
          > <m:echoStructAsSimpleTypes xmlns:m="http://soapinterop.org/">
          > <inputStruct>
          > <varInt>42</varInt>
          > <varFloat>.006</varFloat>
          > <varString>foo</varString>
          > </inputStruct>
          > </m:echoStructAsSimpleTypes>
          > </SOAP-ENV:Body>
          > </SOAP-ENV:Envelope>
          >
          > which doesn't use any XML Schema datatypes. My endpoint uses 1999 by
          > default, so it replies with 1999. I may switch to 2001, but it
          > doesn't help in general. Any ideas?
          >
          > > Here is the request for "echo string header":
          > Sorry, my fault, I didn't refresh endpoint. Will accept both
          > SOAPActions now. Thank you.
          >
          > Best wishes, Paul.
          >
          > > <?xml version="1.0" encoding="UTF-8"?>
          > > <SOAP-ENV:Envelope xmlns:SOAP-
          > > ENV="http://schemas.xmlsoap.org/soap/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" SOAP-
          > > ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
          > > >
          > > <SOAP-ENV:Body>
          > > <m:echoStructAsSimpleTypes xmlns:m="http://soapinterop.org/">
          > > <inputStruct>
          > > <varInt>42</varInt>
          > > <varFloat>.006</varFloat>
          > > <varString>foo</varString>
          > > </inputStruct>
          > > </m:echoStructAsSimpleTypes>
          > > </SOAP-ENV:Body>
          > > </SOAP-ENV:Envelope>
          > >
          > > Here is the response:
          > >
          > > <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
          > > xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
          > > xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
          > > xmlns:xsd="http://www.w3.org/1999/XMLSchema" SOAP-
          > > ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
          > > xmlns:SOAP-
          > > ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-
          > > ENV:Body><namesp1:echoStructAsSimpleTypesResponse
          > > xmlns:namesp1="http://soapinterop.org/"><outputString
          > > xsi:type="xsd:string">foo</outputString><outputInteger
          > > xsi:type="xsd:int">42</outputInteger><outputFloat
          > > xsi:type="xsd:float">.006</outputFloat></namesp1:echoStructAsSi
          > > mpleTypesResponse></SOAP-ENV:Body></SOAP-
          > > ENV:Envelope>
          > >
          > > Here is the request for "echo string header":
          > >
          > > <?xml version="1.0" encoding="UTF-8"?>
          > > <SOAP-ENV:Envelope xmlns:SOAP-
          > > ENV="http://schemas.xmlsoap.org/soap/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" SOAP-
          > > ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
          > > >
          > > <SOAP-ENV:Header>
          > > <h:echoMeStringRequest
          > > xmlns:h="http://soapinterop.org/echoheader/" SOAP-
          > > ENV:actor="http://schemas.xmlsoap.org/soap/actor/next">foo</h:e
          > > choMeStringRequest>
          > > </SOAP-ENV:Header>
          > > <SOAP-ENV:Body>
          > > <m:echoVoid xmlns:m="http://soapinterop.org/">
          > > </m:echoVoid>
          > > </SOAP-ENV:Body>
          > > </SOAP-ENV:Envelope>
          > >
          > > Here is the response:
          > >
          > > <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
          > > xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
          > > xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
          > > xmlns:xsd="http://www.w3.org/1999/XMLSchema" SOAP-
          > > ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
          > > xmlns:SOAP-
          > > ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-
          > > ENV:Body><SOAP-ENV:Fault><faultcode
          > > xsi:type="xsd:string">SOAP-ENV:Client</faultcode><faultstring
          > > xsi:type="xsd:string">SOAPAction '"http://soapinterop.org/"' shall
          > > match quoted 'urn:soapinterop'
          > > </faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-
          > > ENV:Envelope>
          > >
          > > Thanks,
          > >
          > > RC
          > > > Hi, Bob!
          > > >
          > > > --- Bob Cunnings <cunnings@...> wrote:
          > > > > Having some trouble there...
          > > > > Group B: response uses 1999 Schema
          > > > > Group C: is expecting SOAPAction "urn:soapinterop"
          > > > > rather than "http://soapinterop.org/"
          > > > wiredumps? it replies 1999 on 1999 and 2001 on 2001 for me. It
          > > also
          > > > allows both "urn:soapinterop" and "http://soapinterop.org/" as
          > > > SOAPAction. Could it be something else?
          > > >
          > > > Best wishes, Paul.
          > > >
          > > > --- Bob Cunnings <cunnings@...> wrote:
          > > > > Paul,
          > > > >
          > > > > Having some trouble there...
          > > > >
          > > > > Group B: response uses 1999 Schema
          > > > >
          > > > > Group C: is expecting SOAPAction "urn:soapinterop"
          > > > > rather than "http://soapinterop.org/"
          > > > >
          > > > > RC
          > > > >
          > > > > > Hi, Bob!
          > > > > >
          > > > > > > No, I just updated the WM client results mentioned below to
          > >
          > > > > > > include SOAP:Lite, so you should see them there.
          > > > > > I see SOAP::Lite only in [1], but not in [2] or [3]. What
          > > should
          > > > > I do
          > > > > > to be there? :)
          > > > > >
          > > > > > > Maybe you can can get a wire dump at your end.
          > > > > > Should be fixed now.
          > > > > >
          > > > > > Best wishes, Paul.
          > > > > >
          > > > > > [1] http://www.whitemesa.com/interop/results/results.htm
          > > > > > [2] http://www.whitemesa.com/interop/results/b/results.htm
          > > > > > [3] http://www.whitemesa.com/interop/results/c/results.htm
          > > > > >
          > > > > > --- Bob Cunnings <cunnings@...> wrote:
          > > > > > > Paul,
          > > > > > >
          > > > > > > No, I just updated the WM client results mentioned below to
          > >
          > > > > > > include SOAP:Lite, so you should see them there.
          > > > > > >
          > > > > > > I've had trouble with echoFloatArray on the SOAP:Lite
          > > endpoint
          > > > > all
          > > > > > > along, but I can' get a wire dump since the same virtual
          > > > > hosting
          > > > > > > problem that Sam mentioned prevents me from using tcpTrace.
          > > > > > > I get 404 from your endpoint since the host header get
          > > passed
          > > > > > > straight through tcpTrace, and it's naming the local host
          > > here,
          > > > > of
          > > > > > > course.
          > > > > > >
          > > > > > > Maybe you can can get a wire dump at your end.
          > > > > > >
          > > > > > > RC
          > > > > > >
          > > > > > >
          > > > > > > > Hi, Bob!
          > > > > > > >
          > > > > > > > > [1]
          > > http://www.whitemesa.com/interop/results/results.htm
          > > > > > > > There is still some problem with echoFloatArray with
          > > > > SOAP::Lite,
          > > > > > > but
          > > > > > > > I don't see wiredump there.
          > > > > > > >
          > > > > > > > Do I need to be regirstered to get into results for Group
          > > B
          > > > > and
          > > > > > > Group
          > > > > > > > C? Thank you.
          > > > > > > >
          > > > > > > > Best wishes, Paul.
          > > > > > > >
          > > > > > > > --- Bob Cunnings <cunnings@...> wrote:
          > > > > > > > > Hello,
          > > > > > > > >
          > > > > > > > > Ran tests with WM client...
          > > > > > > > >
          > > > > > > > > "base" methods: echoStruct, echoStructArray faulting
          > > for
          > > > > .NET
          > > > > > > > > Remoting endpoint [1]
          > > > > > > > >
          > > > > > > > > "Group B" : echoNestedStruct, echoNestedArray faulting
          > > for
          > > > > .NET
          > > > > > >
          > > > > > > > > Remoting endpoint [2]
          > > > > > > > >
          > > > > > > > > "Group C": returned "string" header entry element in
          > > wrong
          > > > > > > > > namespace, headers targeted at "default" actor not
          > > > > recognized
          > > > > > > for
          > > > > > > > > ASP.NET [3]
          > > > > > > > >
          > > > > > > > > RC
          > > > > > > > >
          > > > > > > > > [1]
          > > http://www.whitemesa.com/interop/results/results.htm
          > > > > > > > > [2]
          > > http://www.whitemesa.com/interop/results/b/results.htm
          > > > > > > > > [3]
          > > http://www.whitemesa.com/interop/results/c/results.htm
          > > > > > > > >
          > > > > > > > >
          > >
          > === message truncated ===
          >
          >
          > __________________________________________________
          > Do You Yahoo!?
          > Make international calls for as low as $.04/minute with Yahoo! Messenger
          > http://phonecard.yahoo.com/
          >
          >
          > -----------------------------------------------------------------
          > This group is a forum for builders of SOAP implementations to discuss
          implementation and interoperability issues. Please stay on-topic.
          >
          > To unsubscribe from this group, send an email to:
          > soapbuilders-unsubscribe@yahoogroups.com
          >
          >
          >
          > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
          >
          >
        • Sam Ruby
          ... I send element name echoBase64 (per the WhiteMesa WSDL), you expect inputByteArray . This means that I get null responses, which are marked as
          Message 4 of 22 , Aug 3, 2001
          • 0 Attachment
            Keith Ballinger wrote:
            >
            > echoBase64 is fixed now. My bad there.

            I send element name "echoBase64" (per the WhiteMesa WSDL), you expect
            "inputByteArray". This means that I get null responses, which are marked
            as failures.

            > As for not seeing the xsi:type info, and the wrong element names, do
            mean the asmx
            > endpoint? I am seeing the type info, and the correct element names....

            I expect element name "return" (per the WhiteMesa WSDL), and you send
            "Return". Note that the SOAP specification indicates that this name should
            not be significant, it is a limitation of the Apache Soap 2.2 design
            (addressed in Axis) that this name matters.

            I double checked, and the xsi:type is present and looks correct. I guess
            that there is a bug in Apache Soap 2.2 dealing with the particular
            combination of multi-ref and array's that ASP.Net is sending.

            - Sam Ruby

            P.S. http://www.mssoapinterop.org/remoting/ServiceA.soap expects
            "echoBase64" and sends "return" and passes both of these tests with Apache
            Soap 2.2.
          • Sam Ruby
            Oops! s/echoBase64/inputBase64/g - Sam Ruby Sam Ruby/Raleigh/IBM@IBMUS on 08/03/2001 08:45:53 AM Please respond to soapbuilders@yahoogroups.com To:
            Message 5 of 22 , Aug 3, 2001
            • 0 Attachment
              Oops! s/echoBase64/inputBase64/g

              - Sam Ruby


              Sam Ruby/Raleigh/IBM@IBMUS on 08/03/2001 08:45:53 AM

              Please respond to soapbuilders@yahoogroups.com

              To: soapbuilders@yahoogroups.com
              cc:
              Subject: RE: [soapbuilders] mssoapinterop.org updated



              Keith Ballinger wrote:
              >
              > echoBase64 is fixed now. My bad there.

              I send element name "echoBase64" (per the WhiteMesa WSDL), you expect
              "inputByteArray". This means that I get null responses, which are marked
              as failures.

              > As for not seeing the xsi:type info, and the wrong element names, do
              mean the asmx
              > endpoint? I am seeing the type info, and the correct element names....

              I expect element name "return" (per the WhiteMesa WSDL), and you send
              "Return". Note that the SOAP specification indicates that this name should
              not be significant, it is a limitation of the Apache Soap 2.2 design
              (addressed in Axis) that this name matters.

              I double checked, and the xsi:type is present and looks correct. I guess
              that there is a bug in Apache Soap 2.2 dealing with the particular
              combination of multi-ref and array's that ASP.Net is sending.

              - Sam Ruby

              P.S. http://www.mssoapinterop.org/remoting/ServiceA.soap expects
              "echoBase64" and sends "return" and passes both of these tests with Apache
              Soap 2.2.



              -----------------------------------------------------------------
              This group is a forum for builders of SOAP implementations to discuss
              implementation and interoperability issues. Please stay on-topic.

              To unsubscribe from this group, send an email to:
              soapbuilders-unsubscribe@yahoogroups.com



              Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
            • Keith Ballinger
              Return has been changed to return. :- ... From: Sam Ruby [mailto:rubys@us.ibm.com] Sent: Friday, August 03, 2001 6:24 AM To: soapbuilders@yahoogroups.com
              Message 6 of 22 , Aug 3, 2001
              • 0 Attachment
                Message
                Return has been changed to return. :->
                -----Original Message-----
                From: Sam Ruby [mailto:rubys@...]
                Sent: Friday, August 03, 2001 6:24 AM
                To: soapbuilders@yahoogroups.com
                Subject: RE: [soapbuilders] mssoapinterop.org updated

                Oops!  s/echoBase64/inputBase64/g

                - Sam Ruby


                Sam Ruby/Raleigh/IBM@IBMUS on 08/03/2001 08:45:53 AM

                Please respond to soapbuilders@yahoogroups.com

                To:   soapbuilders@yahoogroups.com
                cc:
                Subject:  RE: [soapbuilders] mssoapinterop.org updated



                Keith Ballinger wrote:
                >
                > echoBase64 is fixed now. My bad there.

                I send element name "echoBase64" (per the WhiteMesa WSDL), you expect
                "inputByteArray".  This means that I get null responses, which are marked
                as failures.

                > As for  not seeing the xsi:type info, and the wrong element names, do
                mean the asmx
                > endpoint? I am seeing the type info, and the correct element  names....

                I expect element name "return" (per the WhiteMesa WSDL), and you send
                "Return".  Note that the SOAP specification indicates that this name should
                not be significant, it is a limitation of the Apache Soap 2.2 design
                (addressed in Axis) that this name matters.

                I double checked, and the xsi:type is present and looks correct.  I guess
                that there is a bug in Apache Soap 2.2 dealing with the particular
                combination of multi-ref and array's that ASP.Net is sending.

                - Sam Ruby

                P.S.  http://www.mssoapinterop.org/remoting/ServiceA.soap expects
                "echoBase64" and sends "return" and passes both of these tests with Apache
                Soap 2.2.



                -----------------------------------------------------------------
                This group is a forum for builders of SOAP implementations to discuss
                implementation and interoperability issues.  Please stay on-topic.

                To unsubscribe from this group, send an email to:
                soapbuilders-unsubscribe@yahoogroups.com



                Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/





                -----------------------------------------------------------------
                This group is a forum for builders of SOAP implementations to discuss implementation and interoperability issues.  Please stay on-topic.

                To unsubscribe from this group, send an email to:
                soapbuilders-unsubscribe@yahoogroups.com



                Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
              • Sam Ruby
                ... Now everything fails again for me. **** System.Runtime.Remoting.RemotingException - Invalid SOAPAction specified: http://soapinterop.org/ ... - Sam Ruby
                Message 7 of 22 , Aug 3, 2001
                • 0 Attachment
                  :-(

                  Now everything fails again for me.

                  **** System.Runtime.Remoting.RemotingException - Invalid SOAPAction
                  specified: "http://soapinterop.org/"

                  :-(

                  - Sam Ruby
                • Sam Ruby
                  ... Much better. Only thing remaining is that you need to change to inputBase64... - Sam Ruby
                  Message 8 of 22 , Aug 3, 2001
                  • 0 Attachment
                    Keith Ballinger wrote:
                    >
                    > Return has been changed to return. :->

                    Much better. Only thing remaining is that you need to change to
                    inputBase64...

                    - Sam Ruby
                  • Keith Ballinger
                    DOne. ... From: Sam Ruby [mailto:rubys@us.ibm.com] Sent: Friday, August 03, 2001 1:58 PM To: soapbuilders@yahoogroups.com Subject: RE: [soapbuilders]
                    Message 9 of 22 , Aug 3, 2001
                    • 0 Attachment
                      Message
                      DOne.
                      -----Original Message-----
                      From: Sam Ruby [mailto:rubys@...]
                      Sent: Friday, August 03, 2001 1:58 PM
                      To: soapbuilders@yahoogroups.com
                      Subject: RE: [soapbuilders] mssoapinterop.org updated

                      Keith Ballinger wrote:
                      >
                      > Return  has been changed to return. :->

                      Much better.  Only thing remaining is that you need to change to
                      inputBase64...

                      - Sam Ruby



                      -----------------------------------------------------------------
                      This group is a forum for builders of SOAP implementations to discuss implementation and interoperability issues.  Please stay on-topic.

                      To unsubscribe from this group, send an email to:
                      soapbuilders-unsubscribe@yahoogroups.com



                      Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
                    • Bob Cunnings
                      Hello, Same here. Updated results for base and Group B at: http://www.whitemesa.com/interop/results/results.htm RC
                      Message 10 of 22 , Aug 3, 2001
                      • 0 Attachment
                        Hello,

                        Same here. Updated results for "base" and "Group B" at:

                        http://www.whitemesa.com/interop/results/results.htm

                        RC

                        > :-(
                        >
                        > Now everything fails again for me.
                        >
                        > **** System.Runtime.Remoting.RemotingException - Invalid SOAPAction
                        > specified: "http://soapinterop.org/"
                        >
                        > :-(
                        >
                        > - Sam Ruby
                        >
                        >
                        >
                        > -----------------------------------------------------------------
                        > This group is a forum for builders of SOAP implementations to discuss implementation and interoperability issues. Please stay on-topic.
                        >
                        > To unsubscribe from this group, send an email to:
                        > soapbuilders-unsubscribe@yahoogroups.com
                        >
                        >
                        >
                        > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
                        >
                      Your message has been successfully submitted and would be delivered to recipients shortly.