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

echoVoidSoapHeader with WM

Expand Messages
  • Arun Gupta
    Here is a request envelope for echoVoidSoapHeader (with echoMeStringRequest) to WM XSD Interop endpoint:
    Message 1 of 4 , Oct 3, 2002
    • 0 Attachment
      Here is a request envelope for echoVoidSoapHeader (with
      echoMeStringRequest) to WM XSD Interop endpoint:

      <soap-env:Envelope
      xmlns:soap-env="http://schemas.xmlsoap.org/soap/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/" xmlns:ns1="http://soapinterop.org"
      env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
      <soap-env:Header>
      <echoMeStringRequest xmlns="http://soapinterop.org/"
      soap-env:actor="http://schemas.xmlsoap.org/soap/actor/next">
      <varString xmlns="http://soapinterop.org/echoheader/">Hello
      SOAPBuilders!</varString>
      </echoMeStringRequest>
      </soap-env:Header>
      <soap-env:Body>
      <ns1:echoVoidSoapHeader env:encodingStyle=""/>
      </soap-env:Body>
      </soap-env:Envelope>done

      and the response is:

      <soap-env:Envelope
      xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"
      xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
      <soap-env:Body>
      <echoVoidSoapHeaderResponse xmlns="http://soapinterop.org/"/>
      </soap-env:Body>
      </soap-env:Envelope>

      There is no echoMeStringResponse entry in the header unlike the response
      from ASP.NET endpoint where the response envelope is:

      <soap-env:Header>
      <echoMeStringResponse xmlns="http://soapinterop.org/">
      <varString xmlns="http://soapinterop.org/echoheader/">Hello
      SOAPBuilders!</varString> </echoMeStringResponse>
      </soap-env:Header> <soap-env:Body>
      <echoVoidSoapHeaderResponse xmlns="http://soapinterop.org/"/>
      </soap-env:Body>
      </soap-env:Envelope>

      Seems like WM endpoint is consuming this header.

      Thanks,
      -Arun

      --
      =============================================
      There is only one me, I must live myself!
      There is only one today, I must live itself!
      =============================================
      http://members.tripod.com/~apgupta/index.html
      =============================================
    • Bob Cunnings
      The request looks ok, I ll have to look into this, along with the echoHexBinary problem. Thanks, RC ... implementation and interoperability issues. Please
      Message 2 of 4 , Oct 4, 2002
      • 0 Attachment
        The request looks ok, I'll have to look into this, along with the
        echoHexBinary problem.

        Thanks,

        RC

        > Here is a request envelope for echoVoidSoapHeader (with
        > echoMeStringRequest) to WM XSD Interop endpoint:
        >
        > <soap-env:Envelope
        > xmlns:soap-env="http://schemas.xmlsoap.org/soap/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/" xmlns:ns1="http://soapinterop.org"
        > env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
        > <soap-env:Header>
        > <echoMeStringRequest xmlns="http://soapinterop.org/"
        > soap-env:actor="http://schemas.xmlsoap.org/soap/actor/next">
        > <varString xmlns="http://soapinterop.org/echoheader/">Hello
        > SOAPBuilders!</varString>
        > </echoMeStringRequest>
        > </soap-env:Header>
        > <soap-env:Body>
        > <ns1:echoVoidSoapHeader env:encodingStyle=""/>
        > </soap-env:Body>
        > </soap-env:Envelope>done
        >
        > and the response is:
        >
        > <soap-env:Envelope
        > xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"
        > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
        > <soap-env:Body>
        > <echoVoidSoapHeaderResponse xmlns="http://soapinterop.org/"/>
        > </soap-env:Body>
        > </soap-env:Envelope>
        >
        > There is no echoMeStringResponse entry in the header unlike the response
        > from ASP.NET endpoint where the response envelope is:
        >
        > <soap-env:Header>
        > <echoMeStringResponse xmlns="http://soapinterop.org/">
        > <varString xmlns="http://soapinterop.org/echoheader/">Hello
        > SOAPBuilders!</varString> </echoMeStringResponse>
        > </soap-env:Header> <soap-env:Body>
        > <echoVoidSoapHeaderResponse xmlns="http://soapinterop.org/"/>
        > </soap-env:Body>
        > </soap-env:Envelope>
        >
        > Seems like WM endpoint is consuming this header.
        >
        > Thanks,
        > -Arun
        >
        > --
        > =============================================
        > There is only one me, I must live myself!
        > There is only one today, I must live itself!
        > =============================================
        > http://members.tripod.com/~apgupta/index.html
        > =============================================
        >
        >
        >
        >
        > -----------------------------------------------------------------
        > 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/
        >
        >
        >
      • Bob Cunnings
        The problem is right there in the opening soap:Envelope tag. An encodingStyle value of http://schemas.xmlsoap.org/soap/encoding/ is declared, and the header
        Message 3 of 4 , Oct 4, 2002
        • 0 Attachment
          The problem is right there in the opening "soap:Envelope" tag. An
          encodingStyle value of http://schemas.xmlsoap.org/soap/encoding/ is
          declared, and the header entry is within the scope of this declaration. This
          conflicts with the soap:header definition found in the WSDL, which has
          use="literal" and no encoding. If the "echoMeStringRequest" element was
          adorned with the attribute env:encodingStyle="" to turn off the encoding,
          all should be ok (as is done with the message element in the body,
          "echoVoidSoapHeader").

          The wire dumps found at
          http://www.whitemesa.com/interop/results/r4/wsdl-xsd/results.htm,
          echoVoidSoapHeader (5) and (6) show that both the ASP.NET and WM endpoints
          respond favorably to the unencoded header entry, apparently the ASP.NET
          endpoint ignores the encodingStyle attribute if it is sent (it also responds
          only when actor="next", it doesn't seem want to play the role of "ultimate
          destination" at the moment).

          Thanks,

          RC

          > Here is a request envelope for echoVoidSoapHeader (with
          > echoMeStringRequest) to WM XSD Interop endpoint:
          >
          > <soap-env:Envelope
          > xmlns:soap-env="http://schemas.xmlsoap.org/soap/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/" xmlns:ns1="http://soapinterop.org"
          > env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
          > <soap-env:Header>
          > <echoMeStringRequest xmlns="http://soapinterop.org/"
          > soap-env:actor="http://schemas.xmlsoap.org/soap/actor/next">
          > <varString xmlns="http://soapinterop.org/echoheader/">Hello
          > SOAPBuilders!</varString>
          > </echoMeStringRequest>
          > </soap-env:Header>
          > <soap-env:Body>
          > <ns1:echoVoidSoapHeader env:encodingStyle=""/>
          > </soap-env:Body>
          > </soap-env:Envelope>done
          >
          > and the response is:
          >
          > <soap-env:Envelope
          > xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"
          > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
          > <soap-env:Body>
          > <echoVoidSoapHeaderResponse xmlns="http://soapinterop.org/"/>
          > </soap-env:Body>
          > </soap-env:Envelope>
          >
          > There is no echoMeStringResponse entry in the header unlike the response
          > from ASP.NET endpoint where the response envelope is:
          >
          > <soap-env:Header>
          > <echoMeStringResponse xmlns="http://soapinterop.org/">
          > <varString xmlns="http://soapinterop.org/echoheader/">Hello
          > SOAPBuilders!</varString> </echoMeStringResponse>
          > </soap-env:Header> <soap-env:Body>
          > <echoVoidSoapHeaderResponse xmlns="http://soapinterop.org/"/>
          > </soap-env:Body>
          > </soap-env:Envelope>
          >
          > Seems like WM endpoint is consuming this header.
          >
          > Thanks,
          > -Arun
          >
          > --
          > =============================================
          > There is only one me, I must live myself!
          > There is only one today, I must live itself!
          > =============================================
          > http://members.tripod.com/~apgupta/index.html
          > =============================================
        • Arun Gupta
          The solved it. All XSD Interop tests are now passing with WM. ASP.NET s Interop endpoint is giving 404. Regards, -Arun ... --
          Message 4 of 4 , Oct 5, 2002
          • 0 Attachment
            The solved it. All XSD Interop tests are now passing with WM.

            ASP.NET's Interop endpoint is giving 404.

            Regards,
            -Arun



            Bob Cunnings wrote:

            > The problem is right there in the opening "soap:Envelope" tag. An
            > encodingStyle value of http://schemas.xmlsoap.org/soap/encoding/ is
            > declared, and the header entry is within the scope of this declaration. This
            > conflicts with the soap:header definition found in the WSDL, which has
            > use="literal" and no encoding. If the "echoMeStringRequest" element was
            > adorned with the attribute env:encodingStyle="" to turn off the encoding,
            > all should be ok (as is done with the message element in the body,
            > "echoVoidSoapHeader").
            >
            > The wire dumps found at
            > http://www.whitemesa.com/interop/results/r4/wsdl-xsd/results.htm,
            > echoVoidSoapHeader (5) and (6) show that both the ASP.NET and WM endpoints
            > respond favorably to the unencoded header entry, apparently the ASP.NET
            > endpoint ignores the encodingStyle attribute if it is sent (it also responds
            > only when actor="next", it doesn't seem want to play the role of "ultimate
            > destination" at the moment).
            >
            > Thanks,
            >
            > RC
            >
            > > Here is a request envelope for echoVoidSoapHeader (with
            > > echoMeStringRequest) to WM XSD Interop endpoint:
            > >
            > > <soap-env:Envelope
            > > xmlns:soap-env="http://schemas.xmlsoap.org/soap/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/" xmlns:ns1="http://soapinterop.org"
            > > env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
            > > <soap-env:Header>
            > > <echoMeStringRequest xmlns="http://soapinterop.org/"
            > > soap-env:actor="http://schemas.xmlsoap.org/soap/actor/next">
            > > <varString xmlns="http://soapinterop.org/echoheader/">Hello
            > > SOAPBuilders!</varString>
            > > </echoMeStringRequest>
            > > </soap-env:Header>
            > > <soap-env:Body>
            > > <ns1:echoVoidSoapHeader env:encodingStyle=""/>
            > > </soap-env:Body>
            > > </soap-env:Envelope>done
            > >
            > > and the response is:
            > >
            > > <soap-env:Envelope
            > > xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"
            > > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
            > > <soap-env:Body>
            > > <echoVoidSoapHeaderResponse xmlns="http://soapinterop.org/"/>
            > > </soap-env:Body>
            > > </soap-env:Envelope>
            > >
            > > There is no echoMeStringResponse entry in the header unlike the response
            > > from ASP.NET endpoint where the response envelope is:
            > >
            > > <soap-env:Header>
            > > <echoMeStringResponse xmlns="http://soapinterop.org/">
            > > <varString xmlns="http://soapinterop.org/echoheader/">Hello
            > > SOAPBuilders!</varString> </echoMeStringResponse>
            > > </soap-env:Header> <soap-env:Body>
            > > <echoVoidSoapHeaderResponse xmlns="http://soapinterop.org/"/>
            > > </soap-env:Body>
            > > </soap-env:Envelope>
            > >
            > > Seems like WM endpoint is consuming this header.
            > >
            > > Thanks,
            > > -Arun
            > >
            > > --
            > > =============================================
            > > There is only one me, I must live myself!
            > > There is only one today, I must live itself!
            > > =============================================
            > > http://members.tripod.com/~apgupta/index.html
            > > =============================================
            >
            >
            >
            >
            >
            > Yahoo! Groups Sponsor
            > ADVERTISEMENT
            > <http://rd.yahoo.com/M=213858.2436161.3858594.2225242/D=egroupweb/S=1705701014:HM/A=763352/R=0/*http://www.classmates.com/index.tf?s=5085>
            >
            >
            > -----------------------------------------------------------------
            > 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
            > <http://docs.yahoo.com/info/terms/>.


            --
            =============================================
            There is only one me, I must live myself!
            There is only one today, I must live itself!
            =============================================
            http://members.tripod.com/~apgupta/index.html
            =============================================
          Your message has been successfully submitted and would be delivered to recipients shortly.