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

Logging Intermediary

Expand Messages
  • Simon Fell
    As an experiment in building SOAP intermediaries, i put together a simple intermediary that does request/response logging, and a log viewer. There s a request
    Message 1 of 28 , Oct 28, 2001
    • 0 Attachment
      As an experiment in building SOAP intermediaries, i put together a
      simple intermediary that does request/response logging, and a log
      viewer.

      There's a request Header that indicates the next hop that the request
      should be sent to [this should probably be moved to SOAP-RP], and the
      response contains a header with the link to the viewer page for that
      capture.

      Here's an example request/response with the headers populated
      <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://schemas.pocketsoap.com/log/2001/01/'
      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:Log S:actor='http://schemas.pocketsoap.com/log/2001/01/'>
      <a:NextHop>http://mayhem/ilab/soap.asp</a:NextHop>
      </a:Log>
      </S:Header>
      <S:Body><d:echoString>
      <inputString b:type='c:string'>Hello World !</inputString>
      </d:echoString>
      </S:Body></S:Envelope>

      <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/">
      <sp:Header xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/">
      <lg:logResults
      xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/">http://63.202.173.234:81/logViewer.aspx?id=9550da03-bf88-425a-87bd-286e97fba9eb</lg:logResults>
      </sp:Header>
      <SOAP-ENV:Body>
      <m:echoStringResponse xmlns:m="http://soapinterop.org/">
      <outputString xsi:type="xsd:string">Hello World !</outputString>
      </m:echoStringResponse>
      </SOAP-ENV:Body></SOAP-ENV:Envelope>

      I'm coming to the conclusion that your average soap client/server
      toolkit doesn't make a good starting point for building
      intermediaries, what do you think ?

      The service is up and running at http://63.202.173.234:81/log.ashx if
      anyone wants to try it out.

      Cheers
      Simon
      www.pocketsoap.com
    • Bob Cunnings
      Hi Simon, Looks good, I ll give it a shot when I get a chance. A similar thing is available at the White Mesa site [1]. This is supported by the normal interop
      Message 2 of 28 , Oct 28, 2001
      • 0 Attachment
        Hi Simon,

        Looks good, I'll give it a shot when I get a chance. A similar thing is
        available at the White Mesa site [1]. This is supported by the normal
        interop endpoint at http://www.whitemesa.net/interop/std.

        If you could be convinced to get a SOAP-RP endpoint running, interop testing
        using multiple hop routing would be possible. A SOAP-RP endpoint is
        available at WM also [2], with schema and WSDL definitions for the test
        service also available. Unfortunately, no other nodes exist at the moment
        for proper testing.

        You may be right about toolkits in general. The WM server, because of the
        circumstances of its origin, had to have intermediary support baked in early
        for gateway duties.

        I hope that more intermediary nodes can be brought up for interop testing in
        the near future. This is a very interesting area.

        Thanks,

        RC

        [1] http://www.whitemesa.net/std/relay/interop_relay_index.htm
        [2] http://www.whitemesa.com/wmsoapsvc_rp.htm

        > As an experiment in building SOAP intermediaries, i put together a
        > simple intermediary that does request/response logging, and a log
        > viewer.
        >
        > There's a request Header that indicates the next hop that the request
        > should be sent to [this should probably be moved to SOAP-RP], and the
        > response contains a header with the link to the viewer page for that
        > capture.
        >
        > Here's an example request/response with the headers populated
        > <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://schemas.pocketsoap.com/log/2001/01/'
        > 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:Log S:actor='http://schemas.pocketsoap.com/log/2001/01/'>
        > <a:NextHop>http://mayhem/ilab/soap.asp</a:NextHop>
        > </a:Log>
        > </S:Header>
        > <S:Body><d:echoString>
        > <inputString b:type='c:string'>Hello World !</inputString>
        > </d:echoString>
        > </S:Body></S:Envelope>
        >
        > <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/">
        > <sp:Header xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/">
        > <lg:logResults
        >
        xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/">http://63.202.173.234:
        81/logViewer.aspx?id=9550da03-bf88-425a-87bd-286e97fba9eb</lg:logResults>
        > </sp:Header>
        > <SOAP-ENV:Body>
        > <m:echoStringResponse xmlns:m="http://soapinterop.org/">
        > <outputString xsi:type="xsd:string">Hello World !</outputString>
        > </m:echoStringResponse>
        > </SOAP-ENV:Body></SOAP-ENV:Envelope>
        >
        > I'm coming to the conclusion that your average soap client/server
        > toolkit doesn't make a good starting point for building
        > intermediaries, what do you think ?
        >
        > The service is up and running at http://63.202.173.234:81/log.ashx if
        > anyone wants to try it out.
        >
        > Cheers
        > Simon
        > www.pocketsoap.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/
        >
        >
      • Bob Cunnings
        Hi Simon, It works fine. I ve put a test client up at: http://www.whitemesa.net/std/relay/echostring_relay_4s4c.htm Apparently it doesn t like actor
        Message 3 of 28 , Oct 28, 2001
        • 0 Attachment
          Hi Simon,

          It works fine. I've put a test client up at:

          http://www.whitemesa.net/std/relay/echostring_relay_4s4c.htm

          Apparently it doesn't like actor
          "http://schemas.xmlsoap.org/soap/actor/next", giving the error "no actor"
          without a SOAP envelope.
          I tried specifying various Round 2 endpoints, some work, some don't, but
          some of them may be down anyway.

          RC

          > As an experiment in building SOAP intermediaries, i put together a
          > simple intermediary that does request/response logging, and a log
          > viewer.
          >
          > There's a request Header that indicates the next hop that the request
          > should be sent to [this should probably be moved to SOAP-RP], and the
          > response contains a header with the link to the viewer page for that
          > capture.
          >
          > Here's an example request/response with the headers populated
          > <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://schemas.pocketsoap.com/log/2001/01/'
          > 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:Log S:actor='http://schemas.pocketsoap.com/log/2001/01/'>
          > <a:NextHop>http://mayhem/ilab/soap.asp</a:NextHop>
          > </a:Log>
          > </S:Header>
          > <S:Body><d:echoString>
          > <inputString b:type='c:string'>Hello World !</inputString>
          > </d:echoString>
          > </S:Body></S:Envelope>
          >
          > <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/">
          > <sp:Header xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/">
          > <lg:logResults
          >
          xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/">http://63.202.173.234:
          81/logViewer.aspx?id=9550da03-bf88-425a-87bd-286e97fba9eb</lg:logResults>
          > </sp:Header>
          > <SOAP-ENV:Body>
          > <m:echoStringResponse xmlns:m="http://soapinterop.org/">
          > <outputString xsi:type="xsd:string">Hello World !</outputString>
          > </m:echoStringResponse>
          > </SOAP-ENV:Body></SOAP-ENV:Envelope>
          >
          > I'm coming to the conclusion that your average soap client/server
          > toolkit doesn't make a good starting point for building
          > intermediaries, what do you think ?
          >
          > The service is up and running at http://63.202.173.234:81/log.ashx if
          > anyone wants to try it out.
          >
          > Cheers
          > Simon
          > www.pocketsoap.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/
          >
          >
        • Bob Cunnings
          Hi Simon, Sorry, I forgot to ask... is the Log page viewing feature working yet? I seem to be timing out when trying to use the returned page view URLs. RC ...
          Message 4 of 28 , Oct 28, 2001
          • 0 Attachment
            Hi Simon,

            Sorry, I forgot to ask... is the Log page viewing feature working yet? I
            seem to be timing out when trying to use the returned page view URLs.

            RC

            > As an experiment in building SOAP intermediaries, i put together a
            > simple intermediary that does request/response logging, and a log
            > viewer.
            >
            > There's a request Header that indicates the next hop that the request
            > should be sent to [this should probably be moved to SOAP-RP], and the
            > response contains a header with the link to the viewer page for that
            > capture.
            >
            > Here's an example request/response with the headers populated
            > <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://schemas.pocketsoap.com/log/2001/01/'
            > 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:Log S:actor='http://schemas.pocketsoap.com/log/2001/01/'>
            > <a:NextHop>http://mayhem/ilab/soap.asp</a:NextHop>
            > </a:Log>
            > </S:Header>
            > <S:Body><d:echoString>
            > <inputString b:type='c:string'>Hello World !</inputString>
            > </d:echoString>
            > </S:Body></S:Envelope>
            >
            > <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/">
            > <sp:Header xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/">
            > <lg:logResults
            >
            xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/">http://63.202.173.234:
            81/logViewer.aspx?id=9550da03-bf88-425a-87bd-286e97fba9eb</lg:logResults>
            > </sp:Header>
            > <SOAP-ENV:Body>
            > <m:echoStringResponse xmlns:m="http://soapinterop.org/">
            > <outputString xsi:type="xsd:string">Hello World !</outputString>
            > </m:echoStringResponse>
            > </SOAP-ENV:Body></SOAP-ENV:Envelope>
            >
            > I'm coming to the conclusion that your average soap client/server
            > toolkit doesn't make a good starting point for building
            > intermediaries, what do you think ?
            >
            > The service is up and running at http://63.202.173.234:81/log.ashx if
            > anyone wants to try it out.
            >
            > Cheers
            > Simon
            > www.pocketsoap.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/
            >
            >
          • Simon Fell
            It should be working, you should get back an URL something like http://63.202.173.234:81/logViewer.aspx?id=9550da03-bf88-425a-87bd-286e97fba9eb I ll look at
            Message 5 of 28 , Oct 28, 2001
            • 0 Attachment
              It should be working, you should get back an URL something like

              http://63.202.173.234:81/logViewer.aspx?id=9550da03-bf88-425a-87bd-286e97fba9eb

              I'll look at the actor & SOAP-RP stuff later today.

              Cheers
              Simon


              On Sun, 28 Oct 2001 10:46:50 -0700, in soap you wrote:

              >Hi Simon,
              >
              >Sorry, I forgot to ask... is the Log page viewing feature working yet? I
              >seem to be timing out when trying to use the returned page view URLs.
              >
              >RC
              >
              >> As an experiment in building SOAP intermediaries, i put together a
              >> simple intermediary that does request/response logging, and a log
              >> viewer.
              >>
              >> There's a request Header that indicates the next hop that the request
              >> should be sent to [this should probably be moved to SOAP-RP], and the
              >> response contains a header with the link to the viewer page for that
              >> capture.
              >>
              >> Here's an example request/response with the headers populated
              >> <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://schemas.pocketsoap.com/log/2001/01/'
              >> 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:Log S:actor='http://schemas.pocketsoap.com/log/2001/01/'>
              >> <a:NextHop>http://mayhem/ilab/soap.asp</a:NextHop>
              >> </a:Log>
              >> </S:Header>
              >> <S:Body><d:echoString>
              >> <inputString b:type='c:string'>Hello World !</inputString>
              >> </d:echoString>
              >> </S:Body></S:Envelope>
              >>
              >> <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/">
              >> <sp:Header xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/">
              >> <lg:logResults
              >>
              >xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/">http://63.202.173.234:
              >81/logViewer.aspx?id=9550da03-bf88-425a-87bd-286e97fba9eb</lg:logResults>
              >> </sp:Header>
              >> <SOAP-ENV:Body>
              >> <m:echoStringResponse xmlns:m="http://soapinterop.org/">
              >> <outputString xsi:type="xsd:string">Hello World !</outputString>
              >> </m:echoStringResponse>
              >> </SOAP-ENV:Body></SOAP-ENV:Envelope>
              >>
              >> I'm coming to the conclusion that your average soap client/server
              >> toolkit doesn't make a good starting point for building
              >> intermediaries, what do you think ?
              >>
              >> The service is up and running at http://63.202.173.234:81/log.ashx if
              >> anyone wants to try it out.
              >>
              >> Cheers
              >> Simon
              >> www.pocketsoap.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/
              >>
              >>
              >
              >
              >
              >
              >-----------------------------------------------------------------
              >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
              ... toolkit doesn t make a good starting point for building intermediaries, what do you think ? I agree. To build an intermediary, you want to hopefully start
              Message 6 of 28 , Oct 28, 2001
              • 0 Attachment
                >>I'm coming to the conclusion that your average soap client/server
                toolkit doesn't make a good starting point for building
                intermediaries, what do you think ?

                I agree. To build an intermediary, you want to hopefully start sending our the message without having to buffer it up completely in memory. Most toolkits seem to currently buffer and then deserialize. Of course, the smaller the message, the less this matters.

                Another worry is preserving infoset, or even post-schema-validated infoset. Most toolkits map the XML into native platform types, and if you are building an intermediary, the mapping back out might lose information.

                I'll put up a WS-Routing (SOAP-RP) version of this later this week.

                thanks,
                Keith

                -----Original Message-----
                From: Simon Fell [mailto:soap@...]
                Sent: Sun 10/28/2001 12:27 AM
                To: soapbuilders@yahoogroups.com
                Cc:
                Subject: [soapbuilders] Logging Intermediary


                As an experiment in building SOAP intermediaries, i put together a
                simple intermediary that does request/response logging, and a log
                viewer.

                There's a request Header that indicates the next hop that the request
                should be sent to [this should probably be moved to SOAP-RP], and the
                response contains a header with the link to the viewer page for that
                capture.

                Here's an example request/response with the headers populated
                <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://schemas.pocketsoap.com/log/2001/01/'
                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:Log S:actor='http://schemas.pocketsoap.com/log/2001/01/'>
                <a:NextHop>http://mayhem/ilab/soap.asp</a:NextHop>
                </a:Log>
                </S:Header>
                <S:Body><d:echoString>
                <inputString b:type='c:string'>Hello World !</inputString>
                </d:echoString>
                </S:Body></S:Envelope>

                <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/">
                <sp:Header xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/">
                <lg:logResults
                xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/">http://63.202.173.234:81/logViewer.aspx?id=9550da03-bf88-425a-87bd-286e97fba9eb</lg:logResults>
                </sp:Header>
                <SOAP-ENV:Body>
                <m:echoStringResponse xmlns:m="http://soapinterop.org/">
                <outputString xsi:type="xsd:string">Hello World !</outputString>
                </m:echoStringResponse>
                </SOAP-ENV:Body></SOAP-ENV:Envelope>

                I'm coming to the conclusion that your average soap client/server
                toolkit doesn't make a good starting point for building
                intermediaries, what do you think ?

                The service is up and running at http://63.202.173.234:81/log.ashx if
                anyone wants to try it out.

                Cheers
                Simon
                www.pocketsoap.com


                Yahoo! Groups Sponsor
                <http://rd.yahoo.com/M=212180.1660613.3195489.1269402/D=egroupweb/S=1705701014:HM/A=812075/R=0/*http://www.verisign.com/cgi-bin/go.cgi?a=b178349800057000>
                <http://us.adserver.yahoo.com/l?M=212180.1660613.3195489.1269402/D=egroupmail/S=1705701014:HM/A=812075/rand=667273658>

                -----------------------------------------------------------------
                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/> .
              • Steve Waring
                Hi Simon, The log URL is also timing out for me. I was able to successfully send envelopes without specifying any encodingStyle, and specifying , but my
                Message 7 of 28 , Oct 29, 2001
                • 0 Attachment
                  Hi Simon,

                  The log URL is also timing out for me.

                  I was able to successfully send envelopes without specifying any
                  encodingStyle, and specifying "", but my reading of Section 5 is that in
                  soap-enc, the NextHop element should be unqualified.

                  Your example shows the header inheriting soap-enc encodingStyle. Since
                  NextHop is qualified, is the Log element correctly encoded?

                  Thanks
                  Steve
                  www.dolphinharbor.org
                • Bob Cunnings
                  Hi Steve, IMO, Section 5 doesn t exclude the use of struct members with qualified names. It all depends on the definition of the type. From Section 5.4.1 [1]
                  Message 8 of 28 , Oct 29, 2001
                  • 0 Attachment
                    Hi Steve,

                    IMO, Section 5 doesn't exclude the use of struct members with qualified names. It all depends on the definition of the type. From Section 5.4.1 [1]

                    "The members of a Compound Value are encoded as accessor elements. When accessors are distinguished by their name (as for example in a struct), the accessor name is used as the element name. Accessors whose names are local to their containing types have unqualified element names; all others have qualified names."

                    Certainly, if serializing a C struct, the names would be unqualified, but it's easy to imagine the other case. The SOAP-RP schema[2] comes to mind. In this case the accessor names for members of the "path_t" type need to be qualified, as these members' names are not "local to their containing type".

                    RC

                    [1] http://www.w3.org/TR/SOAP/#_Toc478383520
                    [2] http://schemas.xmlsoap.org/rp/


                    > Hi Simon,
                    >
                    > The log URL is also timing out for me.
                    >
                    > I was able to successfully send envelopes without specifying any
                    > encodingStyle, and specifying "", but my reading of Section 5 is that in
                    > soap-enc, the NextHop element should be unqualified.
                    >
                    > Your example shows the header inheriting soap-enc encodingStyle. Since
                    > NextHop is qualified, is the Log element correctly encoded?
                    >
                    > Thanks
                    > Steve
                    > www.dolphinharbor.org
                    >
                    >
                    >
                    >
                    > -----------------------------------------------------------------
                    > 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/
                    >
                    >
                  • Simon Fell
                    ... but you can post to the intermediary ok ? I seem to be cursed with some connectivity problems, such are the joys of being unemployed :( ... Opps, the
                    Message 9 of 28 , Oct 29, 2001
                    • 0 Attachment
                      On Tue, 30 Oct 2001 00:45:21 +1100, in soap you wrote:

                      >Hi Simon,
                      >
                      >The log URL is also timing out for me.

                      but you can post to the intermediary ok ? I seem to be cursed with
                      some connectivity problems, such are the joys of being unemployed :(

                      >I was able to successfully send envelopes without specifying any
                      >encodingStyle, and specifying "", but my reading of Section 5 is that in
                      >soap-enc, the NextHop element should be unqualified.
                      >
                      >Your example shows the header inheriting soap-enc encodingStyle. Since
                      >NextHop is qualified, is the Log element correctly encoded?

                      Opps, the example is wrong !, the header isn't supposed to be section
                      5 encoded, but rather literal XML.

                      Cheers
                      Simon
                    • Simon Fell
                      I have a SOAP-RP enabled version of the logger running at http://63.202.173.234:81/log-rp.ashx which i ve been testing in conjunction with the White Mesa
                      Message 10 of 28 , Oct 29, 2001
                      • 0 Attachment
                        I have a SOAP-RP enabled version of the logger running at
                        http://63.202.173.234:81/log-rp.ashx which i've been testing in
                        conjunction with the White Mesa SOAP-RP enabled endpoint.

                        I'll try and get a SOAP-RP enabled endpoint up and running as well.

                        Cheers
                        Simon
                        www.pocketsoap.com


                        On Sun, 28 Oct 2001 07:16:53 -0700, in soap you wrote:

                        >Hi Simon,
                        >
                        >Looks good, I'll give it a shot when I get a chance. A similar thing is
                        >available at the White Mesa site [1]. This is supported by the normal
                        >interop endpoint at http://www.whitemesa.net/interop/std.
                        >
                        >If you could be convinced to get a SOAP-RP endpoint running, interop testing
                        >using multiple hop routing would be possible. A SOAP-RP endpoint is
                        >available at WM also [2], with schema and WSDL definitions for the test
                        >service also available. Unfortunately, no other nodes exist at the moment
                        >for proper testing.
                        >
                        >You may be right about toolkits in general. The WM server, because of the
                        >circumstances of its origin, had to have intermediary support baked in early
                        >for gateway duties.
                        >
                        >I hope that more intermediary nodes can be brought up for interop testing in
                        >the near future. This is a very interesting area.
                        >
                        >Thanks,
                        >
                        >RC
                        >
                        >[1] http://www.whitemesa.net/std/relay/interop_relay_index.htm
                        >[2] http://www.whitemesa.com/wmsoapsvc_rp.htm
                        >
                        >> As an experiment in building SOAP intermediaries, i put together a
                        >> simple intermediary that does request/response logging, and a log
                        >> viewer.
                        >>
                        >> There's a request Header that indicates the next hop that the request
                        >> should be sent to [this should probably be moved to SOAP-RP], and the
                        >> response contains a header with the link to the viewer page for that
                        >> capture.
                        >>
                        >> Here's an example request/response with the headers populated
                        >> <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://schemas.pocketsoap.com/log/2001/01/'
                        >> 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:Log S:actor='http://schemas.pocketsoap.com/log/2001/01/'>
                        >> <a:NextHop>http://mayhem/ilab/soap.asp</a:NextHop>
                        >> </a:Log>
                        >> </S:Header>
                        >> <S:Body><d:echoString>
                        >> <inputString b:type='c:string'>Hello World !</inputString>
                        >> </d:echoString>
                        >> </S:Body></S:Envelope>
                        >>
                        >> <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/">
                        >> <sp:Header xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/">
                        >> <lg:logResults
                        >>
                        >xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/">http://63.202.173.234:
                        >81/logViewer.aspx?id=9550da03-bf88-425a-87bd-286e97fba9eb</lg:logResults>
                        >> </sp:Header>
                        >> <SOAP-ENV:Body>
                        >> <m:echoStringResponse xmlns:m="http://soapinterop.org/">
                        >> <outputString xsi:type="xsd:string">Hello World !</outputString>
                        >> </m:echoStringResponse>
                        >> </SOAP-ENV:Body></SOAP-ENV:Envelope>
                        >>
                        >> I'm coming to the conclusion that your average soap client/server
                        >> toolkit doesn't make a good starting point for building
                        >> intermediaries, what do you think ?
                        >>
                        >> The service is up and running at http://63.202.173.234:81/log.ashx if
                        >> anyone wants to try it out.
                        >>
                        >> Cheers
                        >> Simon
                        >> www.pocketsoap.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/
                        >>
                        >>
                        >
                        >
                        >
                        >
                        >-----------------------------------------------------------------
                        >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
                        Hi Simon, I tried to hit your intermediary, but, darn the bad luck, 63.202.173.234 seems to be timing out again. I can t ping it either. C: tracert
                        Message 11 of 28 , Oct 29, 2001
                        • 0 Attachment
                          Hi Simon,

                          I tried to hit your intermediary, but, darn the bad luck,
                          63.202.173.234 seems to be timing out again. I can't ping it either.

                          C:\>tracert 63.202.173.234

                          Tracing route to adsl-63-202-173-234.dsl.snfc21.pacbell.net
                          [63.202.173.234]
                          over a maximum of 30 hops:

                          1 <10 ms <10 ms <10 ms 172.16.1.1
                          2 <10 ms <10 ms <10 ms 172.16.2.28
                          3 <10 ms <10 ms 10 ms 204.134.115.225
                          4 30 ms 30 ms 10 ms rtn-lectro.link.nm.org
                          [198.59.177.157]
                          5 <10 ms 10 ms 10 ms abbeyii.nm.org [129.121.10.7]
                          6 10 ms 20 ms 10 ms 500.Serial3-
                          5.GW1.DEN4.ALTER.NET [157.130.161.11
                          3]
                          7 10 ms 20 ms 10 ms 152.at-5-0-0.XR2.SLT4.ALTER.NET
                          [152.63.92.130]

                          8 120 ms 30 ms 20 ms 278.at-1-0-0.XR2.SLT4.ALTER.NET
                          [152.63.94.114]

                          9 40 ms 100 ms 50 ms 0.so-0-1-0.TL2.SLT4.ALTER.NET
                          [146.188.136.154]

                          10 80 ms 90 ms 80 ms 0.so-7-0-0.TL2.CHI2.ALTER.NET
                          [152.63.146.81]
                          11 80 ms 90 ms 110 ms 0.so-2-0-0.XL2.CHI2.ALTER.NET
                          [152.63.67.110]
                          12 80 ms 90 ms 80 ms POS7-0.BR1.CHI2.ALTER.NET
                          [152.63.64.117]
                          13 60 ms 121 ms 70 ms 204.255.168.242
                          14 60 ms 60 ms 60 ms sl-bb23-chi-14-0.sprintlink.net
                          [144.232.26.102]

                          15 101 ms 90 ms 90 ms sl-bb20-sj-6-0.sprintlink.net
                          [144.232.8.117]
                          16 90 ms 101 ms 100 ms sl-bb21-sj-15-0.sprintlink.net
                          [144.232.3.158]
                          17 100 ms 100 ms 101 ms sl-bb20-stk-10-1.sprintlink.net
                          [144.232.9.166]

                          18 100 ms 100 ms 100 ms sl-gw25-stk-9-0.sprintlink.net
                          [144.232.4.218]
                          19 100 ms 100 ms 110 ms sl-southb-13-0.sprintlink.net
                          [160.81.16.22]
                          20 100 ms 130 ms 170 ms core3-g1-0.snfc21.pbi.net
                          [209.232.130.78]
                          21 190 ms 190 ms 201 ms rback27-fe2-1.snfc21.pbi.NET
                          [216.102.187.154]
                          22 * * * Request timed out.
                          23 * * * Request timed out.
                          24 * * * Request timed out.
                          25 * * * Request timed out.
                          26 * * * Request timed out.
                          27 * * * Request timed out.
                          28 * * * Request timed out.
                          29 * * * Request timed out.
                          30 * * * Request timed out.

                          Trace complete.

                          C:\>

                          RC

                          > I have a SOAP-RP enabled version of the logger running at
                          > http://63.202.173.234:81/log-rp.ashx which i've been testing in
                          > conjunction with the White Mesa SOAP-RP enabled endpoint.
                          >
                          > I'll try and get a SOAP-RP enabled endpoint up and running as well.
                          >
                          > Cheers
                          > Simon
                          > www.pocketsoap.com
                          >
                          >
                        • Simon Fell
                          Hi Bob, is it any better now ? Tx Simon
                          Message 12 of 28 , Oct 29, 2001
                          • 0 Attachment
                            Hi Bob,

                            is it any better now ?

                            Tx
                            Simon

                            On Mon, 29 Oct 2001 10:34:25 -0700, in soap you wrote:

                            >Hi Simon,
                            >
                            >I tried to hit your intermediary, but, darn the bad luck,
                            >63.202.173.234 seems to be timing out again. I can't ping it either.
                            >
                            >C:\>tracert 63.202.173.234
                            >
                            >Tracing route to adsl-63-202-173-234.dsl.snfc21.pacbell.net
                            >[63.202.173.234]
                            >over a maximum of 30 hops:
                            >
                            > 1 <10 ms <10 ms <10 ms 172.16.1.1
                            > 2 <10 ms <10 ms <10 ms 172.16.2.28
                            > 3 <10 ms <10 ms 10 ms 204.134.115.225
                            > 4 30 ms 30 ms 10 ms rtn-lectro.link.nm.org
                            >[198.59.177.157]
                            > 5 <10 ms 10 ms 10 ms abbeyii.nm.org [129.121.10.7]
                            > 6 10 ms 20 ms 10 ms 500.Serial3-
                            >5.GW1.DEN4.ALTER.NET [157.130.161.11
                            >3]
                            > 7 10 ms 20 ms 10 ms 152.at-5-0-0.XR2.SLT4.ALTER.NET
                            >[152.63.92.130]
                            >
                            > 8 120 ms 30 ms 20 ms 278.at-1-0-0.XR2.SLT4.ALTER.NET
                            >[152.63.94.114]
                            >
                            > 9 40 ms 100 ms 50 ms 0.so-0-1-0.TL2.SLT4.ALTER.NET
                            >[146.188.136.154]
                            >
                            > 10 80 ms 90 ms 80 ms 0.so-7-0-0.TL2.CHI2.ALTER.NET
                            >[152.63.146.81]
                            > 11 80 ms 90 ms 110 ms 0.so-2-0-0.XL2.CHI2.ALTER.NET
                            >[152.63.67.110]
                            > 12 80 ms 90 ms 80 ms POS7-0.BR1.CHI2.ALTER.NET
                            >[152.63.64.117]
                            > 13 60 ms 121 ms 70 ms 204.255.168.242
                            > 14 60 ms 60 ms 60 ms sl-bb23-chi-14-0.sprintlink.net
                            >[144.232.26.102]
                            >
                            > 15 101 ms 90 ms 90 ms sl-bb20-sj-6-0.sprintlink.net
                            >[144.232.8.117]
                            > 16 90 ms 101 ms 100 ms sl-bb21-sj-15-0.sprintlink.net
                            >[144.232.3.158]
                            > 17 100 ms 100 ms 101 ms sl-bb20-stk-10-1.sprintlink.net
                            >[144.232.9.166]
                            >
                            > 18 100 ms 100 ms 100 ms sl-gw25-stk-9-0.sprintlink.net
                            >[144.232.4.218]
                            > 19 100 ms 100 ms 110 ms sl-southb-13-0.sprintlink.net
                            >[160.81.16.22]
                            > 20 100 ms 130 ms 170 ms core3-g1-0.snfc21.pbi.net
                            >[209.232.130.78]
                            > 21 190 ms 190 ms 201 ms rback27-fe2-1.snfc21.pbi.NET
                            >[216.102.187.154]
                            > 22 * * * Request timed out.
                            > 23 * * * Request timed out.
                            > 24 * * * Request timed out.
                            > 25 * * * Request timed out.
                            > 26 * * * Request timed out.
                            > 27 * * * Request timed out.
                            > 28 * * * Request timed out.
                            > 29 * * * Request timed out.
                            > 30 * * * Request timed out.
                            >
                            >Trace complete.
                            >
                            >C:\>
                            >
                            >RC
                            >
                            >> I have a SOAP-RP enabled version of the logger running at
                            >> http://63.202.173.234:81/log-rp.ashx which i've been testing in
                            >> conjunction with the White Mesa SOAP-RP enabled endpoint.
                            >>
                            >> I'll try and get a SOAP-RP enabled endpoint up and running as well.
                            >>
                            >> Cheers
                            >> Simon
                            >> www.pocketsoap.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/
                            >
                          • Simon Fell
                            Assuming you can get a connection, there s a SOAP-RP enabled version of the interop endpoint running at http://63.202.173.234:81/ilab-rp.ashx All the SOAP-RP
                            Message 13 of 28 , Oct 29, 2001
                            • 0 Attachment
                              Assuming you can get a connection, there's a SOAP-RP enabled version
                              of the interop endpoint running at
                              http://63.202.173.234:81/ilab-rp.ashx

                              All the SOAP-RP error handling isn't in place yet, but the basics
                              should work fine.

                              Cheers
                              Simon

                              On Mon, 29 Oct 2001 09:04:21 -0800, in soap you wrote:

                              >I have a SOAP-RP enabled version of the logger running at
                              >http://63.202.173.234:81/log-rp.ashx which i've been testing in
                              >conjunction with the White Mesa SOAP-RP enabled endpoint.
                              >
                              >I'll try and get a SOAP-RP enabled endpoint up and running as well.
                              >
                              >Cheers
                              >Simon
                              >www.pocketsoap.com
                              >
                              >
                              >On Sun, 28 Oct 2001 07:16:53 -0700, in soap you wrote:
                              >
                              >>Hi Simon,
                              >>
                              >>Looks good, I'll give it a shot when I get a chance. A similar thing is
                              >>available at the White Mesa site [1]. This is supported by the normal
                              >>interop endpoint at http://www.whitemesa.net/interop/std.
                              >>
                              >>If you could be convinced to get a SOAP-RP endpoint running, interop testing
                              >>using multiple hop routing would be possible. A SOAP-RP endpoint is
                              >>available at WM also [2], with schema and WSDL definitions for the test
                              >>service also available. Unfortunately, no other nodes exist at the moment
                              >>for proper testing.
                              >>
                              >>You may be right about toolkits in general. The WM server, because of the
                              >>circumstances of its origin, had to have intermediary support baked in early
                              >>for gateway duties.
                              >>
                              >>I hope that more intermediary nodes can be brought up for interop testing in
                              >>the near future. This is a very interesting area.
                              >>
                              >>Thanks,
                              >>
                              >>RC
                              >>
                              >>[1] http://www.whitemesa.net/std/relay/interop_relay_index.htm
                              >>[2] http://www.whitemesa.com/wmsoapsvc_rp.htm
                              >>
                              >>> As an experiment in building SOAP intermediaries, i put together a
                              >>> simple intermediary that does request/response logging, and a log
                              >>> viewer.
                              >>>
                              >>> There's a request Header that indicates the next hop that the request
                              >>> should be sent to [this should probably be moved to SOAP-RP], and the
                              >>> response contains a header with the link to the viewer page for that
                              >>> capture.
                              >>>
                              >>> Here's an example request/response with the headers populated
                              >>> <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://schemas.pocketsoap.com/log/2001/01/'
                              >>> 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:Log S:actor='http://schemas.pocketsoap.com/log/2001/01/'>
                              >>> <a:NextHop>http://mayhem/ilab/soap.asp</a:NextHop>
                              >>> </a:Log>
                              >>> </S:Header>
                              >>> <S:Body><d:echoString>
                              >>> <inputString b:type='c:string'>Hello World !</inputString>
                              >>> </d:echoString>
                              >>> </S:Body></S:Envelope>
                              >>>
                              >>> <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/">
                              >>> <sp:Header xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/">
                              >>> <lg:logResults
                              >>>
                              >>xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/">http://63.202.173.234:
                              >>81/logViewer.aspx?id=9550da03-bf88-425a-87bd-286e97fba9eb</lg:logResults>
                              >>> </sp:Header>
                              >>> <SOAP-ENV:Body>
                              >>> <m:echoStringResponse xmlns:m="http://soapinterop.org/">
                              >>> <outputString xsi:type="xsd:string">Hello World !</outputString>
                              >>> </m:echoStringResponse>
                              >>> </SOAP-ENV:Body></SOAP-ENV:Envelope>
                              >>>
                              >>> I'm coming to the conclusion that your average soap client/server
                              >>> toolkit doesn't make a good starting point for building
                              >>> intermediaries, what do you think ?
                              >>>
                              >>> The service is up and running at http://63.202.173.234:81/log.ashx if
                              >>> anyone wants to try it out.
                              >>>
                              >>> Cheers
                              >>> Simon
                              >>> www.pocketsoap.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/
                              >>>
                              >>>
                              >>
                              >>
                              >>
                              >>
                              >>-----------------------------------------------------------------
                              >>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 http://docs.yahoo.com/info/terms/
                              >
                            • Steve Waring
                              ... Hi Simon, Yes, as at 20:20:00 (UTC) on 2001-10-29, I can post to http://63.202.173.234:81/log.ashx (using either http://mayhem/ilab/soap.asp or
                              Message 14 of 28 , Oct 29, 2001
                              • 0 Attachment
                                > "Simon Fell" wrote:
                                > but you can post to the intermediary ok ?

                                Hi Simon,
                                Yes, as at 20:20:00 (UTC) on 2001-10-29, I can post to
                                http://63.202.173.234:81/log.ashx (using either http://mayhem/ilab/soap.asp
                                or http://www.dolphinharbor.org/services/interop2001 as the NextHop) and
                                successfully receive a response. I have not been able to GET the url in the
                                response header. TcpTrace shows the status as connected but no HTTP message
                                received. The only GET response I can get from 63.202.173.234:81 is a 403 on
                                the root path url.

                                >"Bob Cunnings" wrote:
                                > IMO, Section 5 doesn't exclude the use of struct members with qualified
                                names.
                                >It all depends on the definition of the type. From Section 5.4.1 [1]

                                Hi Bob,
                                I had interpreted "types" in that section as a schema type definition, and
                                that complexType definitions should be read as
                                elementFormDefault="unqualified".

                                If a service defines an RPC/Encoded operation similar to the "echoStruct"
                                interop lab operation, but with the type definition in a schema with
                                elementFormDefault="qualified", would it be correct to use qualified names
                                for the structures accessors?

                                In soap-enc encodingStyle, Spray currently forces the schema definition
                                local elements to form="unqualified", along with nillable="true" and
                                minOccurs="0".

                                >The SOAP-RP schema[2] comes to mind

                                The construction of this schema is interesting in that "path_t" uses
                                references to global element declarations. This technique may be the
                                clearest way to define a type which encodes with qualified accessors in both
                                soap-enc encodingStyle and literal encodingStyle.

                                I would prefer to change Sprays interpretation of Section 5, and remove the
                                forcing of form="unqualified", but I dont want to suffer interop problems.
                                Any thoughts on this appreciated.

                                Thanks,
                                Steve
                                www.dolphinharbor.org
                              • Bob Cunnings
                                Hello, It works fine, calling it directly, although it doesn t like it when mustUnderstand= 1 in the request message soap-rp header element. I m going to try
                                Message 15 of 28 , Oct 29, 2001
                                • 0 Attachment
                                  Hello,

                                  It works fine, calling it directly, although it doesn't like it when
                                  mustUnderstand="1" in the request message soap-rp header
                                  element.

                                  I'm going to try to connect via an intermediary as soon as I get a
                                  chance.

                                  Looks good!

                                  RC

                                  > Assuming you can get a connection, there's a SOAP-RP enabled version
                                  > of the interop endpoint running at
                                  > http://63.202.173.234:81/ilab-rp.ashx
                                  >
                                  > All the SOAP-RP error handling isn't in place yet, but the basics
                                  > should work fine.
                                  >
                                  > Cheers
                                  > Simon
                                  >
                                  > On Mon, 29 Oct 2001 09:04:21 -0800, in soap you wrote:
                                  >
                                  > >I have a SOAP-RP enabled version of the logger running at
                                  > >http://63.202.173.234:81/log-rp.ashx which i've been testing in
                                  > >conjunction with the White Mesa SOAP-RP enabled endpoint.
                                  > >
                                  > >I'll try and get a SOAP-RP enabled endpoint up and running as well.
                                  > >
                                  > >Cheers
                                  > >Simon
                                  > >www.pocketsoap.com
                                  > >
                                  > >
                                  > >On Sun, 28 Oct 2001 07:16:53 -0700, in soap you wrote:
                                  > >
                                  > >>Hi Simon,
                                  > >>
                                  > >>Looks good, I'll give it a shot when I get a chance. A similar thing is
                                  > >>available at the White Mesa site [1]. This is supported by the normal
                                  > >>interop endpoint at http://www.whitemesa.net/interop/std.
                                  > >>
                                  > >>If you could be convinced to get a SOAP-RP endpoint running, interop testing
                                  > >>using multiple hop routing would be possible. A SOAP-RP endpoint is
                                  > >>available at WM also [2], with schema and WSDL definitions for the test
                                  > >>service also available. Unfortunately, no other nodes exist at the moment
                                  > >>for proper testing.
                                  > >>
                                  > >>You may be right about toolkits in general. The WM server, because of the
                                  > >>circumstances of its origin, had to have intermediary support baked in early
                                  > >>for gateway duties.
                                  > >>
                                  > >>I hope that more intermediary nodes can be brought up for interop testing in
                                  > >>the near future. This is a very interesting area.
                                  > >>
                                  > >>Thanks,
                                  > >>
                                  > >>RC
                                  > >>
                                  > >>[1] http://www.whitemesa.net/std/relay/interop_relay_index.htm
                                  > >>[2] http://www.whitemesa.com/wmsoapsvc_rp.htm
                                  > >>
                                  > >>> As an experiment in building SOAP intermediaries, i put together a
                                  > >>> simple intermediary that does request/response logging, and a log
                                  > >>> viewer.
                                  > >>>
                                  > >>> There's a request Header that indicates the next hop that the request
                                  > >>> should be sent to [this should probably be moved to SOAP-RP], and the
                                  > >>> response contains a header with the link to the viewer page for that
                                  > >>> capture.
                                  > >>>
                                  > >>> Here's an example request/response with the headers populated
                                  > >>> <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://schemas.pocketsoap.com/log/2001/01/'
                                  > >>> 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:Log S:actor='http://schemas.pocketsoap.com/log/2001/01/'>
                                  > >>> <a:NextHop>http://mayhem/ilab/soap.asp</a:NextHop>
                                  > >>> </a:Log>
                                  > >>> </S:Header>
                                  > >>> <S:Body><d:echoString>
                                  > >>> <inputString b:type='c:string'>Hello World !</inputString>
                                  > >>> </d:echoString>
                                  > >>> </S:Body></S:Envelope>
                                  > >>>
                                  > >>> <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/">
                                  > >>> <sp:Header xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/">
                                  > >>> <lg:logResults
                                  > >>>
                                  > >>xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/">http://63.202.173.234:
                                  > >>81/logViewer.aspx?id=9550da03-bf88-425a-87bd-286e97fba9eb</lg:logResults>
                                  > >>> </sp:Header>
                                  > >>> <SOAP-ENV:Body>
                                  > >>> <m:echoStringResponse xmlns:m="http://soapinterop.org/">
                                  > >>> <outputString xsi:type="xsd:string">Hello World !</outputString>
                                  > >>> </m:echoStringResponse>
                                  > >>> </SOAP-ENV:Body></SOAP-ENV:Envelope>
                                  > >>>
                                  > >>> I'm coming to the conclusion that your average soap client/server
                                  > >>> toolkit doesn't make a good starting point for building
                                  > >>> intermediaries, what do you think ?
                                  > >>>
                                  > >>> The service is up and running at http://63.202.173.234:81/log.ashx if
                                  > >>> anyone wants to try it out.
                                  > >>>
                                  > >>> Cheers
                                  > >>> Simon
                                  > >>> www.pocketsoap.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/
                                  > >>>
                                  > >>>
                                  > >>
                                  > >>
                                  > >>
                                  > >>
                                  > >>-----------------------------------------------------------------
                                  > >>This group is a forum for builders of SOAP implementations to discuss implementation and intero
                                  perability 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 interop
                                  erability 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 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/
                                  >
                                • Simon Fell
                                  ... ahhh, ok, i can see what s happening there, i ll fix that. ... ;-) Cheers Simon
                                  Message 16 of 28 , Oct 29, 2001
                                  • 0 Attachment
                                    On Mon, 29 Oct 2001 17:36:13 -0700, in soap you wrote:

                                    >Hello,
                                    >
                                    >It works fine, calling it directly, although it doesn't like it when
                                    >mustUnderstand="1" in the request message soap-rp header
                                    >element.

                                    ahhh, ok, i can see what's happening there, i'll fix that.

                                    >I'm going to try to connect via an intermediary as soon as I get a
                                    >chance.
                                    >
                                    >Looks good!

                                    ;-)

                                    Cheers
                                    Simon
                                  • Bob Cunnings
                                    Hi Steve, ... This case bothers me, since there seems to be a bit of a conflict between Section 5 locally scoped names are unqualified , and XML Schema which
                                    Message 17 of 28 , Oct 29, 2001
                                    • 0 Attachment
                                      Hi Steve,

                                      > Hi Bob,
                                      > I had interpreted "types" in that section as a schema type definition, and
                                      > that complexType definitions should be read as
                                      > elementFormDefault="unqualified".
                                      >
                                      > If a service defines an RPC/Encoded operation similar to the "echoStruct"
                                      > interop lab operation, but with the type definition in a schema with
                                      > elementFormDefault="qualified", would it be correct to use qualified names
                                      > for the structures accessors?
                                      >

                                      This case bothers me, since there seems to be a bit of a conflict between Section 5 "locally scoped names are unqualified", and XML Schema which allows "qualified locals", locally declared elements whose names are qualified. Per Section 5, the XML instance element names become qualified names by virtue of the accessor itself having a qualified name, yet this breaks the rule "locally scoped names are unqualified". Hmmm. In fact the XML Schema Part 0 Sec. 3.3 [1] takes pains to point out how "qualified locals" differ from globally declared elements in key respects in a way that emphasizes the "local" nature of these "qualified locals", local in the sense that I think Section 5 intends. Please let me know if I'm missing something.

                                      > In soap-enc encodingStyle, Spray currently forces the schema definition
                                      > local elements to form="unqualified", along with nillable="true" and
                                      > minOccurs="0".
                                      >
                                      > >The SOAP-RP schema[2] comes to mind
                                      >
                                      > The construction of this schema is interesting in that "path_t" uses
                                      > references to global element declarations. This technique may be the
                                      > clearest way to define a type which encodes with qualified accessors in both
                                      > soap-enc encodingStyle and literal encodingStyle.
                                      >

                                      Yes, this approach doesn't seem to have any problems... the globally declared elements certainly correspond to the "all others" mentioned in Section 5, which are the opposites of the "Accessors whose names are local to their containing types" discussed there. Of course these "all others have qualified names" and to be honest I hope that these are the only species of compound type accessors with qnames to be encountered in nature!

                                      > I would prefer to change Sprays interpretation of Section 5, and remove the
                                      > forcing of form="unqualified", but I dont want to suffer interop problems.
                                      > Any thoughts on this appreciated.
                                      >

                                      Well, I wonder if allowing elementFormDefault="qualified" would be suitable for Section 5 applications, based on my suspicions given above that it may be problematic. Beyond that, I'm not sure what benefit there would be in doing this in a schema design in the first place, but maybe someone could enlighten me on this subject. I don't know if other implementations support this approach in terms of Section 5 encoding, but FWIW the implementation here can handle only the default elementFormDefault="unqualified" case.

                                      On the other hand, it appears that there is no obstacle in Section 5 rules to serializing compound types whose members are elements with global scope, whose accessors have qualified names. It looks like there will be many instances of schemas like this, WS-Routing being only one example, and I see a clear benefit in defining elements globally (possibly in different namespaces) and using them to compose compound types. My point is that there are good reasons, IMHO, for Section 5 implementors to support the style of schema.

                                      RC

                                      > Thanks,
                                      > Steve
                                      > www.dolphinharbor.org
                                      >
                                      >
                                      >
                                      >
                                      >
                                      >
                                      > -----------------------------------------------------------------
                                      > 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
                                      Hi Simon, Ok, when trying to use the WM intermediary, there s a problem... it s not happy because the 4s4c SOAP-RP endpoint isn t placing an actor attribute
                                      Message 18 of 28 , Oct 30, 2001
                                      • 0 Attachment
                                        Hi Simon,

                                        Ok, when trying to use the WM intermediary, there's a problem... it's not happy because the 4s4c SOAP-RP endpoint isn't placing an "actor" attribute on the header entry it places in the *response* message, and the WM intermediary expects to find "http://schemas.xmlsoap.org/soap/actor/next" at a minimum. You might have noticed that the WM endpoint does this with SOAP-RP headers in the response. With none specified at all, and it being aware that it's not the "default actor", the intermediary thinks that it is not the target of the header entry. It's always seemed to me that headers in response messages need to specify their target, no differently than those in request messages, for all the same reasons. If there are multiple intermediaries in the path, how would header entries in the response message get processed correctly without targeting them at the proper actor (which might be associated with only one of possibly many nodes in the path)? Of course a routing header is most conveniently handled by using actor "next", for obvious reasons. This issue doesn't even exist until you start using intermediaries.

                                        What do you think??

                                        Anyway, looking at the wire dumps, everything is fine, other than this.

                                        RC

                                        > Assuming you can get a connection, there's a SOAP-RP enabled version
                                        > of the interop endpoint running at
                                        > http://63.202.173.234:81/ilab-rp.ashx
                                        >
                                        > All the SOAP-RP error handling isn't in place yet, but the basics
                                        > should work fine.
                                        >
                                        > Cheers
                                        > Simon
                                        >
                                        > On Mon, 29 Oct 2001 09:04:21 -0800, in soap you wrote:
                                        >
                                        > >I have a SOAP-RP enabled version of the logger running at
                                        > >http://63.202.173.234:81/log-rp.ashx which i've been testing in
                                        > >conjunction with the White Mesa SOAP-RP enabled endpoint.
                                        > >
                                        > >I'll try and get a SOAP-RP enabled endpoint up and running as well.
                                        > >
                                        > >Cheers
                                        > >Simon
                                        > >www.pocketsoap.com
                                        > >
                                        > >
                                        > >On Sun, 28 Oct 2001 07:16:53 -0700, in soap you wrote:
                                        > >
                                        > >>Hi Simon,
                                        > >>
                                        > >>Looks good, I'll give it a shot when I get a chance. A similar thing is
                                        > >>available at the White Mesa site [1]. This is supported by the normal
                                        > >>interop endpoint at http://www.whitemesa.net/interop/std.
                                        > >>
                                        > >>If you could be convinced to get a SOAP-RP endpoint running, interop testing
                                        > >>using multiple hop routing would be possible. A SOAP-RP endpoint is
                                        > >>available at WM also [2], with schema and WSDL definitions for the test
                                        > >>service also available. Unfortunately, no other nodes exist at the moment
                                        > >>for proper testing.
                                        > >>
                                        > >>You may be right about toolkits in general. The WM server, because of the
                                        > >>circumstances of its origin, had to have intermediary support baked in early
                                        > >>for gateway duties.
                                        > >>
                                        > >>I hope that more intermediary nodes can be brought up for interop testing in
                                        > >>the near future. This is a very interesting area.
                                        > >>
                                        > >>Thanks,
                                        > >>
                                        > >>RC
                                        > >>
                                        > >>[1] http://www.whitemesa.net/std/relay/interop_relay_index.htm
                                        > >>[2] http://www.whitemesa.com/wmsoapsvc_rp.htm
                                        > >>
                                        > >>> As an experiment in building SOAP intermediaries, i put together a
                                        > >>> simple intermediary that does request/response logging, and a log
                                        > >>> viewer.
                                        > >>>
                                        > >>> There's a request Header that indicates the next hop that the request
                                        > >>> should be sent to [this should probably be moved to SOAP-RP], and the
                                        > >>> response contains a header with the link to the viewer page for that
                                        > >>> capture.
                                        > >>>
                                        > >>> Here's an example request/response with the headers populated
                                        > >>> <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://schemas.pocketsoap.com/log/2001/01/'
                                        > >>> 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:Log S:actor='http://schemas.pocketsoap.com/log/2001/01/'>
                                        > >>> <a:NextHop>http://mayhem/ilab/soap.asp</a:NextHop>
                                        > >>> </a:Log>
                                        > >>> </S:Header>
                                        > >>> <S:Body><d:echoString>
                                        > >>> <inputString b:type='c:string'>Hello World !</inputString>
                                        > >>> </d:echoString>
                                        > >>> </S:Body></S:Envelope>
                                        > >>>
                                        > >>> <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/">
                                        > >>> <sp:Header xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/">
                                        > >>> <lg:logResults
                                        > >>>
                                        > >>xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/">http://63.202.173.234:
                                        > >>81/logViewer.aspx?id=9550da03-bf88-425a-87bd-286e97fba9eb</lg:logResults>
                                        > >>> </sp:Header>
                                        > >>> <SOAP-ENV:Body>
                                        > >>> <m:echoStringResponse xmlns:m="http://soapinterop.org/">
                                        > >>> <outputString xsi:type="xsd:string">Hello World !</outputString>
                                        > >>> </m:echoStringResponse>
                                        > >>> </SOAP-ENV:Body></SOAP-ENV:Envelope>
                                        > >>>
                                        > >>> I'm coming to the conclusion that your average soap client/server
                                        > >>> toolkit doesn't make a good starting point for building
                                        > >>> intermediaries, what do you think ?
                                        > >>>
                                        > >>> The service is up and running at http://63.202.173.234:81/log.ashx if
                                        > >>> anyone wants to try it out.
                                        > >>>
                                        > >>> Cheers
                                        > >>> Simon
                                        > >>> www.pocketsoap.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/
                                        > >>>
                                        > >>>
                                        > >>
                                        > >>
                                        > >>
                                        > >>
                                        > >>-----------------------------------------------------------------
                                        > >>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 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 http://docs.yahoo.com/info/terms/
                                        >
                                        >
                                        >
                                      • Simon Fell
                                        Good point, I ve updated it to set both the actor and mustUnderstand in the response. Cheers Simon
                                        Message 19 of 28 , Oct 30, 2001
                                        • 0 Attachment
                                          Good point, I've updated it to set both the actor and mustUnderstand
                                          in the response.

                                          Cheers
                                          Simon

                                          On Tue, 30 Oct 2001 01:16:27 -0700, in soap you wrote:

                                          >Hi Simon,
                                          >
                                          >Ok, when trying to use the WM intermediary, there's a problem... it's not happy because the 4s4c SOAP-RP endpoint isn't placing an "actor" attribute on the header entry it places in the *response* message, and the WM intermediary expects to find "http://schemas.xmlsoap.org/soap/actor/next" at a minimum. You might have noticed that the WM endpoint does this with SOAP-RP headers in the response. With none specified at all, and it being aware that it's not the "default actor", the intermediary thinks that it is not the target of the header entry. It's always seemed to me that headers in response messages need to specify their target, no differently than those in request messages, for all the same reasons. If there are multiple intermediaries in the path, how would header entries in the response message get processed correctly without targeting them at the proper actor (which might be associated with only one of possibly many nodes in the path)? Of course a routing header is most
                                          >conveniently handled by using actor "next", for obvious reasons. This issue doesn't even exist until you start using intermediaries.
                                          >
                                          >What do you think??
                                          >
                                          >Anyway, looking at the wire dumps, everything is fine, other than this.
                                          >
                                          >RC
                                          >
                                          >> Assuming you can get a connection, there's a SOAP-RP enabled version
                                          >> of the interop endpoint running at
                                          >> http://63.202.173.234:81/ilab-rp.ashx
                                          >>
                                          >> All the SOAP-RP error handling isn't in place yet, but the basics
                                          >> should work fine.
                                          >>
                                          >> Cheers
                                          >> Simon
                                          >>
                                          >> On Mon, 29 Oct 2001 09:04:21 -0800, in soap you wrote:
                                          >>
                                          >> >I have a SOAP-RP enabled version of the logger running at
                                          >> >http://63.202.173.234:81/log-rp.ashx which i've been testing in
                                          >> >conjunction with the White Mesa SOAP-RP enabled endpoint.
                                          >> >
                                          >> >I'll try and get a SOAP-RP enabled endpoint up and running as well.
                                          >> >
                                          >> >Cheers
                                          >> >Simon
                                          >> >www.pocketsoap.com
                                          >> >
                                          >> >
                                          >> >On Sun, 28 Oct 2001 07:16:53 -0700, in soap you wrote:
                                          >> >
                                          >> >>Hi Simon,
                                          >> >>
                                          >> >>Looks good, I'll give it a shot when I get a chance. A similar thing is
                                          >> >>available at the White Mesa site [1]. This is supported by the normal
                                          >> >>interop endpoint at http://www.whitemesa.net/interop/std.
                                          >> >>
                                          >> >>If you could be convinced to get a SOAP-RP endpoint running, interop testing
                                          >> >>using multiple hop routing would be possible. A SOAP-RP endpoint is
                                          >> >>available at WM also [2], with schema and WSDL definitions for the test
                                          >> >>service also available. Unfortunately, no other nodes exist at the moment
                                          >> >>for proper testing.
                                          >> >>
                                          >> >>You may be right about toolkits in general. The WM server, because of the
                                          >> >>circumstances of its origin, had to have intermediary support baked in early
                                          >> >>for gateway duties.
                                          >> >>
                                          >> >>I hope that more intermediary nodes can be brought up for interop testing in
                                          >> >>the near future. This is a very interesting area.
                                          >> >>
                                          >> >>Thanks,
                                          >> >>
                                          >> >>RC
                                          >> >>
                                          >> >>[1] http://www.whitemesa.net/std/relay/interop_relay_index.htm
                                          >> >>[2] http://www.whitemesa.com/wmsoapsvc_rp.htm
                                          >> >>
                                          >> >>> As an experiment in building SOAP intermediaries, i put together a
                                          >> >>> simple intermediary that does request/response logging, and a log
                                          >> >>> viewer.
                                          >> >>>
                                          >> >>> There's a request Header that indicates the next hop that the request
                                          >> >>> should be sent to [this should probably be moved to SOAP-RP], and the
                                          >> >>> response contains a header with the link to the viewer page for that
                                          >> >>> capture.
                                          >> >>>
                                          >> >>> Here's an example request/response with the headers populated
                                          >> >>> <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://schemas.pocketsoap.com/log/2001/01/'
                                          >> >>> 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:Log S:actor='http://schemas.pocketsoap.com/log/2001/01/'>
                                          >> >>> <a:NextHop>http://mayhem/ilab/soap.asp</a:NextHop>
                                          >> >>> </a:Log>
                                          >> >>> </S:Header>
                                          >> >>> <S:Body><d:echoString>
                                          >> >>> <inputString b:type='c:string'>Hello World !</inputString>
                                          >> >>> </d:echoString>
                                          >> >>> </S:Body></S:Envelope>
                                          >> >>>
                                          >> >>> <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/">
                                          >> >>> <sp:Header xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/">
                                          >> >>> <lg:logResults
                                          >> >>>
                                          >> >>xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/">http://63.202.173.234:
                                          >> >>81/logViewer.aspx?id=9550da03-bf88-425a-87bd-286e97fba9eb</lg:logResults>
                                          >> >>> </sp:Header>
                                          >> >>> <SOAP-ENV:Body>
                                          >> >>> <m:echoStringResponse xmlns:m="http://soapinterop.org/">
                                          >> >>> <outputString xsi:type="xsd:string">Hello World !</outputString>
                                          >> >>> </m:echoStringResponse>
                                          >> >>> </SOAP-ENV:Body></SOAP-ENV:Envelope>
                                          >> >>>
                                          >> >>> I'm coming to the conclusion that your average soap client/server
                                          >> >>> toolkit doesn't make a good starting point for building
                                          >> >>> intermediaries, what do you think ?
                                          >> >>>
                                          >> >>> The service is up and running at http://63.202.173.234:81/log.ashx if
                                          >> >>> anyone wants to try it out.
                                          >> >>>
                                          >> >>> Cheers
                                          >> >>> Simon
                                          >> >>> www.pocketsoap.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/
                                          >> >>>
                                          >> >>>
                                          >> >>
                                          >> >>
                                          >> >>
                                          >> >>
                                          >> >>-----------------------------------------------------------------
                                          >> >>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 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 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 http://docs.yahoo.com/info/terms/
                                          >
                                        • Bob Cunnings
                                          Hi Simon, Success! I ve been able to route a request through one or both of the 2 WM nodes to your endpoint. Does your intermediary node support RP yet?
                                          Message 20 of 28 , Oct 30, 2001
                                          • 0 Attachment
                                            Hi Simon,

                                            Success! I've been able to route a request through one or both of
                                            the 2 WM nodes to your endpoint. Does your intermediary node
                                            support RP yet?

                                            Thanks,

                                            RC

                                            > Good point, I've updated it to set both the actor and mustUnderstand
                                            > in the response.
                                            >
                                            > Cheers
                                            > Simon
                                            >
                                            > On Tue, 30 Oct 2001 01:16:27 -0700, in soap you wrote:
                                            >
                                            > >Hi Simon,
                                            > >
                                            > >Ok, when trying to use the WM intermediary, there's a problem... it's not happy because the 4s4c SOAP-RP endpoint isn't placing an "actor" attribute on the header entry it places in the *response* message, and the WM intermediary expects to find "http://schemas.xmlsoap.org/soap/actor/next" at
                                            a minimum. You might have noticed that the WM endpoint does this with SOAP-RP headers in the response. With none specified at all, and it being aware that it's not the "default actor", the intermediary thinks that it is not the target of the header entry. It's always seemed to me that headers in
                                            response messages need to specify their target, no differently than those in request messages, for all the same reasons. If there are multiple intermediaries in the path, how would header entries in the response message get processed correctly without targeting them at the proper actor (which
                                            might be associated with only one of possibly many nodes in the path)? Of course a routing header is most
                                            > >conveniently handled by using actor "next", for obvious reasons. This issue doesn't even exist until you start using intermediaries.
                                            > >
                                            > >What do you think??
                                            > >
                                            > >Anyway, looking at the wire dumps, everything is fine, other than this.
                                            > >
                                            > >RC
                                            > >
                                            > >> Assuming you can get a connection, there's a SOAP-RP enabled version
                                            > >> of the interop endpoint running at
                                            > >> http://63.202.173.234:81/ilab-rp.ashx
                                            > >>
                                            > >> All the SOAP-RP error handling isn't in place yet, but the basics
                                            > >> should work fine.
                                            > >>
                                            > >> Cheers
                                            > >> Simon
                                            > >>
                                            > >> On Mon, 29 Oct 2001 09:04:21 -0800, in soap you wrote:
                                            > >>
                                            > >> >I have a SOAP-RP enabled version of the logger running at
                                            > >> >http://63.202.173.234:81/log-rp.ashx which i've been testing in
                                            > >> >conjunction with the White Mesa SOAP-RP enabled endpoint.
                                            > >> >
                                            > >> >I'll try and get a SOAP-RP enabled endpoint up and running as well.
                                            > >> >
                                            > >> >Cheers
                                            > >> >Simon
                                            > >> >www.pocketsoap.com
                                            > >> >
                                            > >> >
                                            > >> >On Sun, 28 Oct 2001 07:16:53 -0700, in soap you wrote:
                                            > >> >
                                            > >> >>Hi Simon,
                                            > >> >>
                                            > >> >>Looks good, I'll give it a shot when I get a chance. A similar thing is
                                            > >> >>available at the White Mesa site [1]. This is supported by the normal
                                            > >> >>interop endpoint at http://www.whitemesa.net/interop/std.
                                            > >> >>
                                            > >> >>If you could be convinced to get a SOAP-RP endpoint running, interop testing
                                            > >> >>using multiple hop routing would be possible. A SOAP-RP endpoint is
                                            > >> >>available at WM also [2], with schema and WSDL definitions for the test
                                            > >> >>service also available. Unfortunately, no other nodes exist at the moment
                                            > >> >>for proper testing.
                                            > >> >>
                                            > >> >>You may be right about toolkits in general. The WM server, because of the
                                            > >> >>circumstances of its origin, had to have intermediary support baked in early
                                            > >> >>for gateway duties.
                                            > >> >>
                                            > >> >>I hope that more intermediary nodes can be brought up for interop testing in
                                            > >> >>the near future. This is a very interesting area.
                                            > >> >>
                                            > >> >>Thanks,
                                            > >> >>
                                            > >> >>RC
                                            > >> >>
                                            > >> >>[1] http://www.whitemesa.net/std/relay/interop_relay_index.htm
                                            > >> >>[2] http://www.whitemesa.com/wmsoapsvc_rp.htm
                                            > >> >>
                                            > >> >>> As an experiment in building SOAP intermediaries, i put together a
                                            > >> >>> simple intermediary that does request/response logging, and a log
                                            > >> >>> viewer.
                                            > >> >>>
                                            > >> >>> There's a request Header that indicates the next hop that the request
                                            > >> >>> should be sent to [this should probably be moved to SOAP-RP], and the
                                            > >> >>> response contains a header with the link to the viewer page for that
                                            > >> >>> capture.
                                            > >> >>>
                                            > >> >>> Here's an example request/response with the headers populated
                                            > >> >>> <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://schemas.pocketsoap.com/log/2001/01/'
                                            > >> >>> 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:Log S:actor='http://schemas.pocketsoap.com/log/2001/01/'>
                                            > >> >>> <a:NextHop>http://mayhem/ilab/soap.asp</a:NextHop>
                                            > >> >>> </a:Log>
                                            > >> >>> </S:Header>
                                            > >> >>> <S:Body><d:echoString>
                                            > >> >>> <inputString b:type='c:string'>Hello World !</inputString>
                                            > >> >>> </d:echoString>
                                            > >> >>> </S:Body></S:Envelope>
                                            > >> >>>
                                            > >> >>> <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/">
                                            > >> >>> <sp:Header xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/">
                                            > >> >>> <lg:logResults
                                            > >> >>>
                                            > >> >>xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/">http://63.202.173.234:
                                            > >> >>81/logViewer.aspx?id=9550da03-bf88-425a-87bd-286e97fba9eb</lg:logResults>
                                            > >> >>> </sp:Header>
                                            > >> >>> <SOAP-ENV:Body>
                                            > >> >>> <m:echoStringResponse xmlns:m="http://soapinterop.org/">
                                            > >> >>> <outputString xsi:type="xsd:string">Hello World !</outputString>
                                            > >> >>> </m:echoStringResponse>
                                            > >> >>> </SOAP-ENV:Body></SOAP-ENV:Envelope>
                                            > >> >>>
                                            > >> >>> I'm coming to the conclusion that your average soap client/server
                                            > >> >>> toolkit doesn't make a good starting point for building
                                            > >> >>> intermediaries, what do you think ?
                                            > >> >>>
                                            > >> >>> The service is up and running at http://63.202.173.234:81/log.ashx if
                                            > >> >>> anyone wants to try it out.
                                            > >> >>>
                                            > >> >>> Cheers
                                            > >> >>> Simon
                                            > >> >>> www.pocketsoap.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/
                                            > >> >>>
                                            > >> >>>
                                            > >> >>
                                            > >> >>
                                            > >> >>
                                            > >> >>
                                            > >> >>-----------------------------------------------------------------
                                            > >> >>This group is a forum for builders of SOAP implementations to discuss implementation and int
                                            eroperability 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 inte
                                            roperability 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 inter
                                            operability 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 interop
                                            erability 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 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/
                                            >
                                          • Simon Fell
                                            Cool :) There s a SOAP-RP version of the logging intermediary at http://63.202.173.234:81/log-rp.ashx Cheers Simon
                                            Message 21 of 28 , Oct 30, 2001
                                            • 0 Attachment
                                              Cool :)

                                              There's a SOAP-RP version of the logging intermediary at
                                              http://63.202.173.234:81/log-rp.ashx

                                              Cheers
                                              Simon

                                              On Tue, 30 Oct 2001 11:31:20 -0700, in soap you wrote:

                                              >Hi Simon,
                                              >
                                              >Success! I've been able to route a request through one or both of
                                              >the 2 WM nodes to your endpoint. Does your intermediary node
                                              >support RP yet?
                                              >
                                              >Thanks,
                                              >
                                              >RC
                                              >
                                              >> Good point, I've updated it to set both the actor and mustUnderstand
                                              >> in the response.
                                              >>
                                              >> Cheers
                                              >> Simon
                                              >>
                                              >> On Tue, 30 Oct 2001 01:16:27 -0700, in soap you wrote:
                                              >>
                                              >> >Hi Simon,
                                              >> >
                                              >> >Ok, when trying to use the WM intermediary, there's a problem... it's not happy because the 4s4c SOAP-RP endpoint isn't placing an "actor" attribute on the header entry it places in the *response* message, and the WM intermediary expects to find "http://schemas.xmlsoap.org/soap/actor/next" at
                                              >a minimum. You might have noticed that the WM endpoint does this with SOAP-RP headers in the response. With none specified at all, and it being aware that it's not the "default actor", the intermediary thinks that it is not the target of the header entry. It's always seemed to me that headers in
                                              >response messages need to specify their target, no differently than those in request messages, for all the same reasons. If there are multiple intermediaries in the path, how would header entries in the response message get processed correctly without targeting them at the proper actor (which
                                              >might be associated with only one of possibly many nodes in the path)? Of course a routing header is most
                                              >> >conveniently handled by using actor "next", for obvious reasons. This issue doesn't even exist until you start using intermediaries.
                                              >> >
                                              >> >What do you think??
                                              >> >
                                              >> >Anyway, looking at the wire dumps, everything is fine, other than this.
                                              >> >
                                              >> >RC
                                              >> >
                                              >> >> Assuming you can get a connection, there's a SOAP-RP enabled version
                                              >> >> of the interop endpoint running at
                                              >> >> http://63.202.173.234:81/ilab-rp.ashx
                                              >> >>
                                              >> >> All the SOAP-RP error handling isn't in place yet, but the basics
                                              >> >> should work fine.
                                              >> >>
                                              >> >> Cheers
                                              >> >> Simon
                                              >> >>
                                              >> >> On Mon, 29 Oct 2001 09:04:21 -0800, in soap you wrote:
                                              >> >>
                                              >> >> >I have a SOAP-RP enabled version of the logger running at
                                              >> >> >http://63.202.173.234:81/log-rp.ashx which i've been testing in
                                              >> >> >conjunction with the White Mesa SOAP-RP enabled endpoint.
                                              >> >> >
                                              >> >> >I'll try and get a SOAP-RP enabled endpoint up and running as well.
                                              >> >> >
                                              >> >> >Cheers
                                              >> >> >Simon
                                              >> >> >www.pocketsoap.com
                                              >> >> >
                                              >> >> >
                                              >> >> >On Sun, 28 Oct 2001 07:16:53 -0700, in soap you wrote:
                                              >> >> >
                                              >> >> >>Hi Simon,
                                              >> >> >>
                                              >> >> >>Looks good, I'll give it a shot when I get a chance. A similar thing is
                                              >> >> >>available at the White Mesa site [1]. This is supported by the normal
                                              >> >> >>interop endpoint at http://www.whitemesa.net/interop/std.
                                              >> >> >>
                                              >> >> >>If you could be convinced to get a SOAP-RP endpoint running, interop testing
                                              >> >> >>using multiple hop routing would be possible. A SOAP-RP endpoint is
                                              >> >> >>available at WM also [2], with schema and WSDL definitions for the test
                                              >> >> >>service also available. Unfortunately, no other nodes exist at the moment
                                              >> >> >>for proper testing.
                                              >> >> >>
                                              >> >> >>You may be right about toolkits in general. The WM server, because of the
                                              >> >> >>circumstances of its origin, had to have intermediary support baked in early
                                              >> >> >>for gateway duties.
                                              >> >> >>
                                              >> >> >>I hope that more intermediary nodes can be brought up for interop testing in
                                              >> >> >>the near future. This is a very interesting area.
                                              >> >> >>
                                              >> >> >>Thanks,
                                              >> >> >>
                                              >> >> >>RC
                                              >> >> >>
                                              >> >> >>[1] http://www.whitemesa.net/std/relay/interop_relay_index.htm
                                              >> >> >>[2] http://www.whitemesa.com/wmsoapsvc_rp.htm
                                              >> >> >>
                                              >> >> >>> As an experiment in building SOAP intermediaries, i put together a
                                              >> >> >>> simple intermediary that does request/response logging, and a log
                                              >> >> >>> viewer.
                                              >> >> >>>
                                              >> >> >>> There's a request Header that indicates the next hop that the request
                                              >> >> >>> should be sent to [this should probably be moved to SOAP-RP], and the
                                              >> >> >>> response contains a header with the link to the viewer page for that
                                              >> >> >>> capture.
                                              >> >> >>>
                                              >> >> >>> Here's an example request/response with the headers populated
                                              >> >> >>> <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://schemas.pocketsoap.com/log/2001/01/'
                                              >> >> >>> 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:Log S:actor='http://schemas.pocketsoap.com/log/2001/01/'>
                                              >> >> >>> <a:NextHop>http://mayhem/ilab/soap.asp</a:NextHop>
                                              >> >> >>> </a:Log>
                                              >> >> >>> </S:Header>
                                              >> >> >>> <S:Body><d:echoString>
                                              >> >> >>> <inputString b:type='c:string'>Hello World !</inputString>
                                              >> >> >>> </d:echoString>
                                              >> >> >>> </S:Body></S:Envelope>
                                              >> >> >>>
                                              >> >> >>> <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/">
                                              >> >> >>> <sp:Header xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/">
                                              >> >> >>> <lg:logResults
                                              >> >> >>>
                                              >> >> >>xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/">http://63.202.173.234:
                                              >> >> >>81/logViewer.aspx?id=9550da03-bf88-425a-87bd-286e97fba9eb</lg:logResults>
                                              >> >> >>> </sp:Header>
                                              >> >> >>> <SOAP-ENV:Body>
                                              >> >> >>> <m:echoStringResponse xmlns:m="http://soapinterop.org/">
                                              >> >> >>> <outputString xsi:type="xsd:string">Hello World !</outputString>
                                              >> >> >>> </m:echoStringResponse>
                                              >> >> >>> </SOAP-ENV:Body></SOAP-ENV:Envelope>
                                              >> >> >>>
                                              >> >> >>> I'm coming to the conclusion that your average soap client/server
                                              >> >> >>> toolkit doesn't make a good starting point for building
                                              >> >> >>> intermediaries, what do you think ?
                                              >> >> >>>
                                              >> >> >>> The service is up and running at http://63.202.173.234:81/log.ashx if
                                              >> >> >>> anyone wants to try it out.
                                              >> >> >>>
                                              >> >> >>> Cheers
                                              >> >> >>> Simon
                                              >> >> >>> www.pocketsoap.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/
                                              >> >> >>>
                                              >> >> >>>
                                              >> >> >>
                                              >> >> >>
                                              >> >> >>
                                              >> >> >>
                                              >> >> >>-----------------------------------------------------------------
                                              >> >> >>This group is a forum for builders of SOAP implementations to discuss implementation and int
                                              >eroperability 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 inte
                                              >roperability 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 inter
                                              >operability 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 interop
                                              >erability 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 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/
                                              >>
                                              >
                                              >
                                              >
                                              >-----------------------------------------------------------------
                                              >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
                                              Hi Simon, I notice that your RP endpoint doesn t make an entry in the rev reverse path element it includes in the response message (no via child element is
                                              Message 22 of 28 , Oct 30, 2001
                                              • 0 Attachment
                                                Hi Simon,

                                                I notice that your RP endpoint doesn't make an entry in the "rev"
                                                reverse path element it includes in the response message (no "via"
                                                child element is present). Is this intentional? Although the reverse
                                                path element is optional, I believe that if it *is* present, each node
                                                is expected to insert a "via" element into it, including the sender.

                                                What's happening is that if the WM intermediaries see a "rev"
                                                element in the response, they insert a "via" element into it. But the
                                                result is an incomplete reverse path, since it lacks the endpoint's
                                                URL. This might be worse than having no reverse path at all.

                                                What do you think?

                                                RC


                                                > Cool :)
                                                >
                                                > There's a SOAP-RP version of the logging intermediary at
                                                > http://63.202.173.234:81/log-rp.ashx
                                                >
                                                > Cheers
                                                > Simon
                                                >
                                                > On Tue, 30 Oct 2001 11:31:20 -0700, in soap you wrote:
                                                >
                                                > >Hi Simon,
                                                > >
                                                > >Success! I've been able to route a request through one or both of
                                                > >the 2 WM nodes to your endpoint. Does your intermediary node
                                                > >support RP yet?
                                                > >
                                                > >Thanks,
                                                > >
                                                > >RC
                                                > >
                                                > >> Good point, I've updated it to set both the actor and mustUnderstand
                                                > >> in the response.
                                                > >>
                                                > >> Cheers
                                                > >> Simon
                                                > >>
                                                > >> On Tue, 30 Oct 2001 01:16:27 -0700, in soap you wrote:
                                                > >>
                                                > >> >Hi Simon,
                                                > >> >
                                                > >> >Ok, when trying to use the WM intermediary, there's a problem... it's not happy because the 4s4c SOAP-RP endpoint isn't placing an "actor" attribute on the header entry it places in the *response* message, and the WM intermediary expects to find "http://schemas.xmlsoap.org/soap/actor/next"
                                                at
                                                > >a minimum. You might have noticed that the WM endpoint does this with SOAP-RP headers in the response. With none specified at all, and it being aware that it's not the "default actor", the intermediary thinks that it is not the target of the header entry. It's always seemed to me that headers
                                                in
                                                > >response messages need to specify their target, no differently than those in request messages, for all the same reasons. If there are multiple intermediaries in the path, how would header entries in the response message get processed correctly without targeting them at the proper actor (which
                                                > >might be associated with only one of possibly many nodes in the path)? Of course a routing header is most
                                                > >> >conveniently handled by using actor "next", for obvious reasons. This issue doesn't even exist until you start using intermediaries.
                                                > >> >
                                                > >> >What do you think??
                                                > >> >
                                                > >> >Anyway, looking at the wire dumps, everything is fine, other than this.
                                                > >> >
                                                > >> >RC
                                                > >> >
                                                > >> >> Assuming you can get a connection, there's a SOAP-RP enabled version
                                                > >> >> of the interop endpoint running at
                                                > >> >> http://63.202.173.234:81/ilab-rp.ashx
                                                > >> >>
                                                > >> >> All the SOAP-RP error handling isn't in place yet, but the basics
                                                > >> >> should work fine.
                                                > >> >>
                                                > >> >> Cheers
                                                > >> >> Simon
                                                > >> >>
                                                > >> >> On Mon, 29 Oct 2001 09:04:21 -0800, in soap you wrote:
                                                > >> >>
                                                > >> >> >I have a SOAP-RP enabled version of the logger running at
                                                > >> >> >http://63.202.173.234:81/log-rp.ashx which i've been testing in
                                                > >> >> >conjunction with the White Mesa SOAP-RP enabled endpoint.
                                                > >> >> >
                                                > >> >> >I'll try and get a SOAP-RP enabled endpoint up and running as well.
                                                > >> >> >
                                                > >> >> >Cheers
                                                > >> >> >Simon
                                                > >> >> >www.pocketsoap.com
                                                > >> >> >
                                                > >> >> >
                                                > >> >> >On Sun, 28 Oct 2001 07:16:53 -0700, in soap you wrote:
                                                > >> >> >
                                                > >> >> >>Hi Simon,
                                                > >> >> >>
                                                > >> >> >>Looks good, I'll give it a shot when I get a chance. A similar thing is
                                                > >> >> >>available at the White Mesa site [1]. This is supported by the normal
                                                > >> >> >>interop endpoint at http://www.whitemesa.net/interop/std.
                                                > >> >> >>
                                                > >> >> >>If you could be convinced to get a SOAP-RP endpoint running, interop testing
                                                > >> >> >>using multiple hop routing would be possible. A SOAP-RP endpoint is
                                                > >> >> >>available at WM also [2], with schema and WSDL definitions for the test
                                                > >> >> >>service also available. Unfortunately, no other nodes exist at the moment
                                                > >> >> >>for proper testing.
                                                > >> >> >>
                                                > >> >> >>You may be right about toolkits in general. The WM server, because of the
                                                > >> >> >>circumstances of its origin, had to have intermediary support baked in early
                                                > >> >> >>for gateway duties.
                                                > >> >> >>
                                                > >> >> >>I hope that more intermediary nodes can be brought up for interop testing in
                                                > >> >> >>the near future. This is a very interesting area.
                                                > >> >> >>
                                                > >> >> >>Thanks,
                                                > >> >> >>
                                                > >> >> >>RC
                                                > >> >> >>
                                                > >> >> >>[1] http://www.whitemesa.net/std/relay/interop_relay_index.htm
                                                > >> >> >>[2] http://www.whitemesa.com/wmsoapsvc_rp.htm
                                                > >> >> >>
                                                > >> >> >>> As an experiment in building SOAP intermediaries, i put together a
                                                > >> >> >>> simple intermediary that does request/response logging, and a log
                                                > >> >> >>> viewer.
                                                > >> >> >>>
                                                > >> >> >>> There's a request Header that indicates the next hop that the request
                                                > >> >> >>> should be sent to [this should probably be moved to SOAP-RP], and the
                                                > >> >> >>> response contains a header with the link to the viewer page for that
                                                > >> >> >>> capture.
                                                > >> >> >>>
                                                > >> >> >>> Here's an example request/response with the headers populated
                                                > >> >> >>> <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://schemas.pocketsoap.com/log/2001/01/'
                                                > >> >> >>> 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:Log S:actor='http://schemas.pocketsoap.com/log/2001/01/'>
                                                > >> >> >>> <a:NextHop>http://mayhem/ilab/soap.asp</a:NextHop>
                                                > >> >> >>> </a:Log>
                                                > >> >> >>> </S:Header>
                                                > >> >> >>> <S:Body><d:echoString>
                                                > >> >> >>> <inputString b:type='c:string'>Hello World !</inputString>
                                                > >> >> >>> </d:echoString>
                                                > >> >> >>> </S:Body></S:Envelope>
                                                > >> >> >>>
                                                > >> >> >>> <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/">
                                                > >> >> >>> <sp:Header xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/">
                                                > >> >> >>> <lg:logResults
                                                > >> >> >>>
                                                > >> >> >>xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/">http://63.202.173.234:
                                                > >> >> >>81/logViewer.aspx?id=9550da03-bf88-425a-87bd-286e97fba9eb</lg:logResults>
                                                > >> >> >>> </sp:Header>
                                                > >> >> >>> <SOAP-ENV:Body>
                                                > >> >> >>> <m:echoStringResponse xmlns:m="http://soapinterop.org/">
                                                > >> >> >>> <outputString xsi:type="xsd:string">Hello World !</outputString>
                                                > >> >> >>> </m:echoStringResponse>
                                                > >> >> >>> </SOAP-ENV:Body></SOAP-ENV:Envelope>
                                                > >> >> >>>
                                                > >> >> >>> I'm coming to the conclusion that your average soap client/server
                                                > >> >> >>> toolkit doesn't make a good starting point for building
                                                > >> >> >>> intermediaries, what do you think ?
                                                > >> >> >>>
                                                > >> >> >>> The service is up and running at http://63.202.173.234:81/log.ashx if
                                                > >> >> >>> anyone wants to try it out.
                                                > >> >> >>>
                                                > >> >> >>> Cheers
                                                > >> >> >>> Simon
                                                > >> >> >>> www.pocketsoap.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/
                                                > >> >> >>>
                                                > >> >> >>>
                                                > >> >> >>
                                                > >> >> >>
                                                > >> >> >>
                                                > >> >> >>
                                                > >> >> >>-----------------------------------------------------------------
                                                > >> >> >>This group is a forum for builders of SOAP implementations to discuss implementation and
                                                int
                                                > >eroperability 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 i
                                                nte
                                                > >roperability 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 in
                                                ter
                                                > >operability 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 inte
                                                rop
                                                > >erability 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 inter
                                                ope
                                                > >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/
                                                > >>
                                                > >
                                                > >
                                                > >
                                                > >-----------------------------------------------------------------
                                                > >This group is a forum for builders of SOAP implementations to discuss implementation and interop
                                                erability 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 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/
                                                >
                                              • Simon Fell
                                                Hi Bob, I ll have to read the spec again, i thought the via elements were for intermediaries, therefore the server shouldn t enter one in the reverse path.
                                                Message 23 of 28 , Oct 30, 2001
                                                • 0 Attachment
                                                  Hi Bob,

                                                  I'll have to read the spec again, i thought the via elements were for
                                                  intermediaries, therefore the server shouldn't enter one in the
                                                  reverse path.

                                                  Cheers
                                                  Simon

                                                  On Tue, 30 Oct 2001 14:35:27 -0700, in soap you wrote:

                                                  >Hi Simon,
                                                  >
                                                  >I notice that your RP endpoint doesn't make an entry in the "rev"
                                                  >reverse path element it includes in the response message (no "via"
                                                  >child element is present). Is this intentional? Although the reverse
                                                  >path element is optional, I believe that if it *is* present, each node
                                                  >is expected to insert a "via" element into it, including the sender.
                                                  >
                                                  >What's happening is that if the WM intermediaries see a "rev"
                                                  >element in the response, they insert a "via" element into it. But the
                                                  >result is an incomplete reverse path, since it lacks the endpoint's
                                                  >URL. This might be worse than having no reverse path at all.
                                                  >
                                                  >What do you think?
                                                  >
                                                  >RC
                                                  >
                                                  >
                                                  >> Cool :)
                                                  >>
                                                  >> There's a SOAP-RP version of the logging intermediary at
                                                  >> http://63.202.173.234:81/log-rp.ashx
                                                  >>
                                                  >> Cheers
                                                  >> Simon
                                                  >>
                                                  >> On Tue, 30 Oct 2001 11:31:20 -0700, in soap you wrote:
                                                  >>
                                                  >> >Hi Simon,
                                                  >> >
                                                  >> >Success! I've been able to route a request through one or both of
                                                  >> >the 2 WM nodes to your endpoint. Does your intermediary node
                                                  >> >support RP yet?
                                                  >> >
                                                  >> >Thanks,
                                                  >> >
                                                  >> >RC
                                                  >> >
                                                  >> >> Good point, I've updated it to set both the actor and mustUnderstand
                                                  >> >> in the response.
                                                  >> >>
                                                  >> >> Cheers
                                                  >> >> Simon
                                                  >> >>
                                                  >> >> On Tue, 30 Oct 2001 01:16:27 -0700, in soap you wrote:
                                                  >> >>
                                                  >> >> >Hi Simon,
                                                  >> >> >
                                                  >> >> >Ok, when trying to use the WM intermediary, there's a problem... it's not happy because the 4s4c SOAP-RP endpoint isn't placing an "actor" attribute on the header entry it places in the *response* message, and the WM intermediary expects to find "http://schemas.xmlsoap.org/soap/actor/next"
                                                  >at
                                                  >> >a minimum. You might have noticed that the WM endpoint does this with SOAP-RP headers in the response. With none specified at all, and it being aware that it's not the "default actor", the intermediary thinks that it is not the target of the header entry. It's always seemed to me that headers
                                                  >in
                                                  >> >response messages need to specify their target, no differently than those in request messages, for all the same reasons. If there are multiple intermediaries in the path, how would header entries in the response message get processed correctly without targeting them at the proper actor (which
                                                  >> >might be associated with only one of possibly many nodes in the path)? Of course a routing header is most
                                                  >> >> >conveniently handled by using actor "next", for obvious reasons. This issue doesn't even exist until you start using intermediaries.
                                                  >> >> >
                                                  >> >> >What do you think??
                                                  >> >> >
                                                  >> >> >Anyway, looking at the wire dumps, everything is fine, other than this.
                                                  >> >> >
                                                  >> >> >RC
                                                  >> >> >
                                                  >> >> >> Assuming you can get a connection, there's a SOAP-RP enabled version
                                                  >> >> >> of the interop endpoint running at
                                                  >> >> >> http://63.202.173.234:81/ilab-rp.ashx
                                                  >> >> >>
                                                  >> >> >> All the SOAP-RP error handling isn't in place yet, but the basics
                                                  >> >> >> should work fine.
                                                  >> >> >>
                                                  >> >> >> Cheers
                                                  >> >> >> Simon
                                                  >> >> >>
                                                  >> >> >> On Mon, 29 Oct 2001 09:04:21 -0800, in soap you wrote:
                                                  >> >> >>
                                                  >> >> >> >I have a SOAP-RP enabled version of the logger running at
                                                  >> >> >> >http://63.202.173.234:81/log-rp.ashx which i've been testing in
                                                  >> >> >> >conjunction with the White Mesa SOAP-RP enabled endpoint.
                                                  >> >> >> >
                                                  >> >> >> >I'll try and get a SOAP-RP enabled endpoint up and running as well.
                                                  >> >> >> >
                                                  >> >> >> >Cheers
                                                  >> >> >> >Simon
                                                  >> >> >> >www.pocketsoap.com
                                                  >> >> >> >
                                                  >> >> >> >
                                                  >> >> >> >On Sun, 28 Oct 2001 07:16:53 -0700, in soap you wrote:
                                                  >> >> >> >
                                                  >> >> >> >>Hi Simon,
                                                  >> >> >> >>
                                                  >> >> >> >>Looks good, I'll give it a shot when I get a chance. A similar thing is
                                                  >> >> >> >>available at the White Mesa site [1]. This is supported by the normal
                                                  >> >> >> >>interop endpoint at http://www.whitemesa.net/interop/std.
                                                  >> >> >> >>
                                                  >> >> >> >>If you could be convinced to get a SOAP-RP endpoint running, interop testing
                                                  >> >> >> >>using multiple hop routing would be possible. A SOAP-RP endpoint is
                                                  >> >> >> >>available at WM also [2], with schema and WSDL definitions for the test
                                                  >> >> >> >>service also available. Unfortunately, no other nodes exist at the moment
                                                  >> >> >> >>for proper testing.
                                                  >> >> >> >>
                                                  >> >> >> >>You may be right about toolkits in general. The WM server, because of the
                                                  >> >> >> >>circumstances of its origin, had to have intermediary support baked in early
                                                  >> >> >> >>for gateway duties.
                                                  >> >> >> >>
                                                  >> >> >> >>I hope that more intermediary nodes can be brought up for interop testing in
                                                  >> >> >> >>the near future. This is a very interesting area.
                                                  >> >> >> >>
                                                  >> >> >> >>Thanks,
                                                  >> >> >> >>
                                                  >> >> >> >>RC
                                                  >> >> >> >>
                                                  >> >> >> >>[1] http://www.whitemesa.net/std/relay/interop_relay_index.htm
                                                  >> >> >> >>[2] http://www.whitemesa.com/wmsoapsvc_rp.htm
                                                  >> >> >> >>
                                                  >> >> >> >>> As an experiment in building SOAP intermediaries, i put together a
                                                  >> >> >> >>> simple intermediary that does request/response logging, and a log
                                                  >> >> >> >>> viewer.
                                                  >> >> >> >>>
                                                  >> >> >> >>> There's a request Header that indicates the next hop that the request
                                                  >> >> >> >>> should be sent to [this should probably be moved to SOAP-RP], and the
                                                  >> >> >> >>> response contains a header with the link to the viewer page for that
                                                  >> >> >> >>> capture.
                                                  >> >> >> >>>
                                                  >> >> >> >>> Here's an example request/response with the headers populated
                                                  >> >> >> >>> <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://schemas.pocketsoap.com/log/2001/01/'
                                                  >> >> >> >>> 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:Log S:actor='http://schemas.pocketsoap.com/log/2001/01/'>
                                                  >> >> >> >>> <a:NextHop>http://mayhem/ilab/soap.asp</a:NextHop>
                                                  >> >> >> >>> </a:Log>
                                                  >> >> >> >>> </S:Header>
                                                  >> >> >> >>> <S:Body><d:echoString>
                                                  >> >> >> >>> <inputString b:type='c:string'>Hello World !</inputString>
                                                  >> >> >> >>> </d:echoString>
                                                  >> >> >> >>> </S:Body></S:Envelope>
                                                  >> >> >> >>>
                                                  >> >> >> >>> <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/">
                                                  >> >> >> >>> <sp:Header xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/">
                                                  >> >> >> >>> <lg:logResults
                                                  >> >> >> >>>
                                                  >> >> >> >>xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/">http://63.202.173.234:
                                                  >> >> >> >>81/logViewer.aspx?id=9550da03-bf88-425a-87bd-286e97fba9eb</lg:logResults>
                                                  >> >> >> >>> </sp:Header>
                                                  >> >> >> >>> <SOAP-ENV:Body>
                                                  >> >> >> >>> <m:echoStringResponse xmlns:m="http://soapinterop.org/">
                                                  >> >> >> >>> <outputString xsi:type="xsd:string">Hello World !</outputString>
                                                  >> >> >> >>> </m:echoStringResponse>
                                                  >> >> >> >>> </SOAP-ENV:Body></SOAP-ENV:Envelope>
                                                  >> >> >> >>>
                                                  >> >> >> >>> I'm coming to the conclusion that your average soap client/server
                                                  >> >> >> >>> toolkit doesn't make a good starting point for building
                                                  >> >> >> >>> intermediaries, what do you think ?
                                                  >> >> >> >>>
                                                  >> >> >> >>> The service is up and running at http://63.202.173.234:81/log.ashx if
                                                  >> >> >> >>> anyone wants to try it out.
                                                  >> >> >> >>>
                                                  >> >> >> >>> Cheers
                                                  >> >> >> >>> Simon
                                                  >> >> >> >>> www.pocketsoap.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/
                                                  >> >> >> >>>
                                                  >> >> >> >>>
                                                  >> >> >> >>
                                                  >> >> >> >>
                                                  >> >> >> >>
                                                  >> >> >> >>
                                                  >> >> >> >>-----------------------------------------------------------------
                                                  >> >> >> >>This group is a forum for builders of SOAP implementations to discuss implementation and
                                                  >int
                                                  >> >eroperability 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 i
                                                  >nte
                                                  >> >roperability 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 in
                                                  >ter
                                                  >> >operability 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 inte
                                                  >rop
                                                  >> >erability 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 inter
                                                  >ope
                                                  >> >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/
                                                  >> >>
                                                  >> >
                                                  >> >
                                                  >> >
                                                  >> >-----------------------------------------------------------------
                                                  >> >This group is a forum for builders of SOAP implementations to discuss implementation and interop
                                                  >erability 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 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/
                                                  >>
                                                  >
                                                  >
                                                  >
                                                  >
                                                  >-----------------------------------------------------------------
                                                  >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/
                                                  >
                                                • Simon Fell
                                                  Bob, you re correct [of course !], I ve updated my endpoint accordingly. Cheers Simon www.pocketsoap.com
                                                  Message 24 of 28 , Nov 3, 2001
                                                  • 0 Attachment
                                                    Bob, you're correct [of course !], I've updated my endpoint
                                                    accordingly.

                                                    Cheers
                                                    Simon
                                                    www.pocketsoap.com

                                                    On Tue, 30 Oct 2001 14:07:39 -0800, in soap you wrote:

                                                    >Hi Bob,
                                                    >
                                                    >I'll have to read the spec again, i thought the via elements were for
                                                    >intermediaries, therefore the server shouldn't enter one in the
                                                    >reverse path.
                                                    >
                                                    >Cheers
                                                    >Simon
                                                    >
                                                    >On Tue, 30 Oct 2001 14:35:27 -0700, in soap you wrote:
                                                    >
                                                    >>Hi Simon,
                                                    >>
                                                    >>I notice that your RP endpoint doesn't make an entry in the "rev"
                                                    >>reverse path element it includes in the response message (no "via"
                                                    >>child element is present). Is this intentional? Although the reverse
                                                    >>path element is optional, I believe that if it *is* present, each node
                                                    >>is expected to insert a "via" element into it, including the sender.
                                                    >>
                                                    >>What's happening is that if the WM intermediaries see a "rev"
                                                    >>element in the response, they insert a "via" element into it. But the
                                                    >>result is an incomplete reverse path, since it lacks the endpoint's
                                                    >>URL. This might be worse than having no reverse path at all.
                                                    >>
                                                    >>What do you think?
                                                    >>
                                                    >>RC
                                                    >>
                                                    >>
                                                    >>> Cool :)
                                                    >>>
                                                    >>> There's a SOAP-RP version of the logging intermediary at
                                                    >>> http://63.202.173.234:81/log-rp.ashx
                                                    >>>
                                                    >>> Cheers
                                                    >>> Simon
                                                    >>>
                                                    >>> On Tue, 30 Oct 2001 11:31:20 -0700, in soap you wrote:
                                                    >>>
                                                    >>> >Hi Simon,
                                                    >>> >
                                                    >>> >Success! I've been able to route a request through one or both of
                                                    >>> >the 2 WM nodes to your endpoint. Does your intermediary node
                                                    >>> >support RP yet?
                                                    >>> >
                                                    >>> >Thanks,
                                                    >>> >
                                                    >>> >RC
                                                    >>> >
                                                    >>> >> Good point, I've updated it to set both the actor and mustUnderstand
                                                    >>> >> in the response.
                                                    >>> >>
                                                    >>> >> Cheers
                                                    >>> >> Simon
                                                    >>> >>
                                                    >>> >> On Tue, 30 Oct 2001 01:16:27 -0700, in soap you wrote:
                                                    >>> >>
                                                    >>> >> >Hi Simon,
                                                    >>> >> >
                                                    >>> >> >Ok, when trying to use the WM intermediary, there's a problem... it's not happy because the 4s4c SOAP-RP endpoint isn't placing an "actor" attribute on the header entry it places in the *response* message, and the WM intermediary expects to find "http://schemas.xmlsoap.org/soap/actor/next"
                                                    >>at
                                                    >>> >a minimum. You might have noticed that the WM endpoint does this with SOAP-RP headers in the response. With none specified at all, and it being aware that it's not the "default actor", the intermediary thinks that it is not the target of the header entry. It's always seemed to me that headers
                                                    >>in
                                                    >>> >response messages need to specify their target, no differently than those in request messages, for all the same reasons. If there are multiple intermediaries in the path, how would header entries in the response message get processed correctly without targeting them at the proper actor (which
                                                    >>> >might be associated with only one of possibly many nodes in the path)? Of course a routing header is most
                                                    >>> >> >conveniently handled by using actor "next", for obvious reasons. This issue doesn't even exist until you start using intermediaries.
                                                    >>> >> >
                                                    >>> >> >What do you think??
                                                    >>> >> >
                                                    >>> >> >Anyway, looking at the wire dumps, everything is fine, other than this.
                                                    >>> >> >
                                                    >>> >> >RC
                                                    >>> >> >
                                                    >>> >> >> Assuming you can get a connection, there's a SOAP-RP enabled version
                                                    >>> >> >> of the interop endpoint running at
                                                    >>> >> >> http://63.202.173.234:81/ilab-rp.ashx
                                                    >>> >> >>
                                                    >>> >> >> All the SOAP-RP error handling isn't in place yet, but the basics
                                                    >>> >> >> should work fine.
                                                    >>> >> >>
                                                    >>> >> >> Cheers
                                                    >>> >> >> Simon
                                                    >>> >> >>
                                                    >>> >> >> On Mon, 29 Oct 2001 09:04:21 -0800, in soap you wrote:
                                                    >>> >> >>
                                                    >>> >> >> >I have a SOAP-RP enabled version of the logger running at
                                                    >>> >> >> >http://63.202.173.234:81/log-rp.ashx which i've been testing in
                                                    >>> >> >> >conjunction with the White Mesa SOAP-RP enabled endpoint.
                                                    >>> >> >> >
                                                    >>> >> >> >I'll try and get a SOAP-RP enabled endpoint up and running as well.
                                                    >>> >> >> >
                                                    >>> >> >> >Cheers
                                                    >>> >> >> >Simon
                                                    >>> >> >> >www.pocketsoap.com
                                                    >>> >> >> >
                                                    >>> >> >> >
                                                    >>> >> >> >On Sun, 28 Oct 2001 07:16:53 -0700, in soap you wrote:
                                                    >>> >> >> >
                                                    >>> >> >> >>Hi Simon,
                                                    >>> >> >> >>
                                                    >>> >> >> >>Looks good, I'll give it a shot when I get a chance. A similar thing is
                                                    >>> >> >> >>available at the White Mesa site [1]. This is supported by the normal
                                                    >>> >> >> >>interop endpoint at http://www.whitemesa.net/interop/std.
                                                    >>> >> >> >>
                                                    >>> >> >> >>If you could be convinced to get a SOAP-RP endpoint running, interop testing
                                                    >>> >> >> >>using multiple hop routing would be possible. A SOAP-RP endpoint is
                                                    >>> >> >> >>available at WM also [2], with schema and WSDL definitions for the test
                                                    >>> >> >> >>service also available. Unfortunately, no other nodes exist at the moment
                                                    >>> >> >> >>for proper testing.
                                                    >>> >> >> >>
                                                    >>> >> >> >>You may be right about toolkits in general. The WM server, because of the
                                                    >>> >> >> >>circumstances of its origin, had to have intermediary support baked in early
                                                    >>> >> >> >>for gateway duties.
                                                    >>> >> >> >>
                                                    >>> >> >> >>I hope that more intermediary nodes can be brought up for interop testing in
                                                    >>> >> >> >>the near future. This is a very interesting area.
                                                    >>> >> >> >>
                                                    >>> >> >> >>Thanks,
                                                    >>> >> >> >>
                                                    >>> >> >> >>RC
                                                    >>> >> >> >>
                                                    >>> >> >> >>[1] http://www.whitemesa.net/std/relay/interop_relay_index.htm
                                                    >>> >> >> >>[2] http://www.whitemesa.com/wmsoapsvc_rp.htm
                                                    >>> >> >> >>
                                                    >>> >> >> >>> As an experiment in building SOAP intermediaries, i put together a
                                                    >>> >> >> >>> simple intermediary that does request/response logging, and a log
                                                    >>> >> >> >>> viewer.
                                                    >>> >> >> >>>
                                                    >>> >> >> >>> There's a request Header that indicates the next hop that the request
                                                    >>> >> >> >>> should be sent to [this should probably be moved to SOAP-RP], and the
                                                    >>> >> >> >>> response contains a header with the link to the viewer page for that
                                                    >>> >> >> >>> capture.
                                                    >>> >> >> >>>
                                                    >>> >> >> >>> Here's an example request/response with the headers populated
                                                    >>> >> >> >>> <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://schemas.pocketsoap.com/log/2001/01/'
                                                    >>> >> >> >>> 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:Log S:actor='http://schemas.pocketsoap.com/log/2001/01/'>
                                                    >>> >> >> >>> <a:NextHop>http://mayhem/ilab/soap.asp</a:NextHop>
                                                    >>> >> >> >>> </a:Log>
                                                    >>> >> >> >>> </S:Header>
                                                    >>> >> >> >>> <S:Body><d:echoString>
                                                    >>> >> >> >>> <inputString b:type='c:string'>Hello World !</inputString>
                                                    >>> >> >> >>> </d:echoString>
                                                    >>> >> >> >>> </S:Body></S:Envelope>
                                                    >>> >> >> >>>
                                                    >>> >> >> >>> <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/">
                                                    >>> >> >> >>> <sp:Header xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/">
                                                    >>> >> >> >>> <lg:logResults
                                                    >>> >> >> >>>
                                                    >>> >> >> >>xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/">http://63.202.173.234:
                                                    >>> >> >> >>81/logViewer.aspx?id=9550da03-bf88-425a-87bd-286e97fba9eb</lg:logResults>
                                                    >>> >> >> >>> </sp:Header>
                                                    >>> >> >> >>> <SOAP-ENV:Body>
                                                    >>> >> >> >>> <m:echoStringResponse xmlns:m="http://soapinterop.org/">
                                                    >>> >> >> >>> <outputString xsi:type="xsd:string">Hello World !</outputString>
                                                    >>> >> >> >>> </m:echoStringResponse>
                                                    >>> >> >> >>> </SOAP-ENV:Body></SOAP-ENV:Envelope>
                                                    >>> >> >> >>>
                                                    >>> >> >> >>> I'm coming to the conclusion that your average soap client/server
                                                    >>> >> >> >>> toolkit doesn't make a good starting point for building
                                                    >>> >> >> >>> intermediaries, what do you think ?
                                                    >>> >> >> >>>
                                                    >>> >> >> >>> The service is up and running at http://63.202.173.234:81/log.ashx if
                                                    >>> >> >> >>> anyone wants to try it out.
                                                    >>> >> >> >>>
                                                    >>> >> >> >>> Cheers
                                                    >>> >> >> >>> Simon
                                                    >>> >> >> >>> www.pocketsoap.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/
                                                    >>> >> >> >>>
                                                    >>> >> >> >>>
                                                    >>> >> >> >>
                                                    >>> >> >> >>
                                                    >>> >> >> >>
                                                    >>> >> >> >>
                                                    >>> >> >> >>-----------------------------------------------------------------
                                                    >>> >> >> >>This group is a forum for builders of SOAP implementations to discuss implementation and
                                                    >>int
                                                    >>> >eroperability 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 i
                                                    >>nte
                                                    >>> >roperability 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 in
                                                    >>ter
                                                    >>> >operability 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 inte
                                                    >>rop
                                                    >>> >erability 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 inter
                                                    >>ope
                                                    >>> >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/
                                                    >>> >>
                                                    >>> >
                                                    >>> >
                                                    >>> >
                                                    >>> >-----------------------------------------------------------------
                                                    >>> >This group is a forum for builders of SOAP implementations to discuss implementation and interop
                                                    >>erability 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 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/
                                                    >>>
                                                    >>
                                                    >>
                                                    >>
                                                    >>
                                                    >>-----------------------------------------------------------------
                                                    >>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 http://docs.yahoo.com/info/terms/
                                                    >
                                                  • yzhang@motherbot.com
                                                    Hi Simon, When I sent the following message to log-rp.ashx:
                                                    Message 25 of 28 , Nov 3, 2001
                                                    • 0 Attachment
                                                      Hi Simon,

                                                      When I sent the following message to log-rp.ashx:


                                                      <?xml version="1.0" encoding="UTF-8" standalone="no"?>
                                                      <SOAP-ENV:Envelope xmlns:SOAP-
                                                      ENV="http://schemas.xmlsoap.org/soap/envelope/"
                                                      xmlns:tns="http://www.xmethods.net/sd/TemperatureService.wsdl"
                                                      xmlns:xsd="http://www.w3.org/1999/XMLSchema"
                                                      xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
                                                      xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:SOAP-
                                                      ENC="http://schemas.xmlsoap.org/soap/encoding/" SOAP-
                                                      ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-
                                                      ENV:Header><mm:path xmlns:mm="http://schemas.xmlsoap.org/rp/" SOAP-
                                                      ENV:actor="http://schemas.xmlsoap.org/soap/actor/next" SOAP-
                                                      ENV:mustUnderstand="1"><mm:action></mm:action><mm:to>http://services.x
                                                      methods.net:80/soap/servlet/rpcrouter</mm:to><mm:id>5efd520d-d0c4-
                                                      11d5-8fe6-
                                                      00105a24f6d1</mm:id><mm:fwd><mm:via>http://63.202.173.234:81/log-
                                                      rp.ashx</mm:via></mm:fwd><mm:rev><mm:via/></mm:rev></mm:path></SOAP-
                                                      ENV:Header> <SOAP-ENV:Body><mns:getTemp xmlns:mns="urn:xmethods-
                                                      Temperature"><zipcode
                                                      xsi:type="xsd:string">20876</zipcode></mns:getTemp></SOAP-ENV:Body>
                                                      </SOAP-ENV:Envelope>

                                                      I got a fault message back,

                                                      <sp:Envelope
                                                      xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/"><sp:Body><sp:Faul
                                                      t><faultcode>sp:Client</faultcode><faultstring>Value null was found
                                                      where an instance of an object was
                                                      required.</faultstring><faultactor>http://schemas.pocketsoap.com/log/2
                                                      001/01/</faultactor><detail><lg:StackTrace
                                                      xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/"> at
                                                      logiRP.InboundRPProcessing(XmlNode rpNode) in C:\soap\dotnetsoap\log-
                                                      rp.ashx:line 149

                                                      at logiRP.ProcessRequest(HttpContext context) in
                                                      C:\soap\dotnetsoap\log-rp.ashx:line
                                                      60</lg:StackTrace></detail></sp:Fault></sp:Body></sp:Envelope>


                                                      Any idea what's wong in the request?

                                                      Thanks!

                                                      Yunhao




                                                      --- In soapbuilders@y..., Simon Fell <soap@z...> wrote:
                                                      > Bob, you're correct [of course !], I've updated my endpoint
                                                      > accordingly.
                                                      >
                                                      > Cheers
                                                      > Simon
                                                      > www.pocketsoap.com
                                                      >
                                                      > On Tue, 30 Oct 2001 14:07:39 -0800, in soap you wrote:
                                                      >
                                                      > >Hi Bob,
                                                      > >
                                                      > >I'll have to read the spec again, i thought the via elements were
                                                      for
                                                      > >intermediaries, therefore the server shouldn't enter one in the
                                                      > >reverse path.
                                                      > >
                                                      > >Cheers
                                                      > >Simon
                                                      > >
                                                      > >On Tue, 30 Oct 2001 14:35:27 -0700, in soap you wrote:
                                                      > >
                                                      > >>Hi Simon,
                                                      > >>
                                                      > >>I notice that your RP endpoint doesn't make an entry in the "rev"
                                                      > >>reverse path element it includes in the response message
                                                      (no "via"
                                                      > >>child element is present). Is this intentional? Although the
                                                      reverse
                                                      > >>path element is optional, I believe that if it *is* present, each
                                                      node
                                                      > >>is expected to insert a "via" element into it, including the
                                                      sender.
                                                      > >>
                                                      > >>What's happening is that if the WM intermediaries see a "rev"
                                                      > >>element in the response, they insert a "via" element into it. But
                                                      the
                                                      > >>result is an incomplete reverse path, since it lacks the
                                                      endpoint's
                                                      > >>URL. This might be worse than having no reverse path at all.
                                                      > >>
                                                      > >>What do you think?
                                                      > >>
                                                      > >>RC
                                                      > >>
                                                      > >>
                                                      > >>> Cool :)
                                                      > >>>
                                                      > >>> There's a SOAP-RP version of the logging intermediary at
                                                      > >>> http://63.202.173.234:81/log-rp.ashx
                                                      > >>>
                                                      > >>> Cheers
                                                      > >>> Simon
                                                      > >>>
                                                      > >>> On Tue, 30 Oct 2001 11:31:20 -0700, in soap you wrote:
                                                      > >>>
                                                      > >>> >Hi Simon,
                                                      > >>> >
                                                      > >>> >Success! I've been able to route a request through one or both
                                                      of
                                                      > >>> >the 2 WM nodes to your endpoint. Does your intermediary node
                                                      > >>> >support RP yet?
                                                      > >>> >
                                                      > >>> >Thanks,
                                                      > >>> >
                                                      > >>> >RC
                                                      > >>> >
                                                      > >>> >> Good point, I've updated it to set both the actor and
                                                      mustUnderstand
                                                      > >>> >> in the response.
                                                      > >>> >>
                                                      > >>> >> Cheers
                                                      > >>> >> Simon
                                                      > >>> >>
                                                      > >>> >> On Tue, 30 Oct 2001 01:16:27 -0700, in soap you wrote:
                                                      > >>> >>
                                                      > >>> >> >Hi Simon,
                                                      > >>> >> >
                                                      > >>> >> >Ok, when trying to use the WM intermediary, there's a
                                                      problem... it's not happy because the 4s4c SOAP-RP endpoint isn't
                                                      placing an "actor" attribute on the header entry it places in the
                                                      *response* message, and the WM intermediary expects to
                                                      find "http://schemas.xmlsoap.org/soap/actor/next"
                                                      > >>at
                                                      > >>> >a minimum. You might have noticed that the WM endpoint does
                                                      this with SOAP-RP headers in the response. With none specified at
                                                      all, and it being aware that it's not the "default actor", the
                                                      intermediary thinks that it is not the target of the header entry.
                                                      It's always seemed to me that headers
                                                      > >>in
                                                      > >>> >response messages need to specify their target, no differently
                                                      than those in request messages, for all the same reasons. If there
                                                      are multiple intermediaries in the path, how would header entries in
                                                      the response message get processed correctly without targeting them
                                                      at the proper actor (which
                                                      > >>> >might be associated with only one of possibly many nodes in
                                                      the path)? Of course a routing header is most
                                                      > >>> >> >conveniently handled by using actor "next", for obvious
                                                      reasons. This issue doesn't even exist until you start using
                                                      intermediaries.
                                                      > >>> >> >
                                                      > >>> >> >What do you think??
                                                      > >>> >> >
                                                      > >>> >> >Anyway, looking at the wire dumps, everything is fine,
                                                      other than this.
                                                      > >>> >> >
                                                      > >>> >> >RC
                                                      > >>> >> >
                                                      > >>> >> >> Assuming you can get a connection, there's a SOAP-RP
                                                      enabled version
                                                      > >>> >> >> of the interop endpoint running at
                                                      > >>> >> >> http://63.202.173.234:81/ilab-rp.ashx
                                                      > >>> >> >>
                                                      > >>> >> >> All the SOAP-RP error handling isn't in place yet, but
                                                      the basics
                                                      > >>> >> >> should work fine.
                                                      > >>> >> >>
                                                      > >>> >> >> Cheers
                                                      > >>> >> >> Simon
                                                      > >>> >> >>
                                                      > >>> >> >> On Mon, 29 Oct 2001 09:04:21 -0800, in soap you wrote:
                                                      > >>> >> >>
                                                      > >>> >> >> >I have a SOAP-RP enabled version of the logger running
                                                      at
                                                      > >>> >> >> >http://63.202.173.234:81/log-rp.ashx which i've been
                                                      testing in
                                                      > >>> >> >> >conjunction with the White Mesa SOAP-RP enabled endpoint.
                                                      > >>> >> >> >
                                                      > >>> >> >> >I'll try and get a SOAP-RP enabled endpoint up and
                                                      running as well.
                                                      > >>> >> >> >
                                                      > >>> >> >> >Cheers
                                                      > >>> >> >> >Simon
                                                      > >>> >> >> >www.pocketsoap.com
                                                      > >>> >> >> >
                                                      > >>> >> >> >
                                                      > >>> >> >> >On Sun, 28 Oct 2001 07:16:53 -0700, in soap you wrote:
                                                      > >>> >> >> >
                                                      > >>> >> >> >>Hi Simon,
                                                      > >>> >> >> >>
                                                      > >>> >> >> >>Looks good, I'll give it a shot when I get a chance. A
                                                      similar thing is
                                                      > >>> >> >> >>available at the White Mesa site [1]. This is supported
                                                      by the normal
                                                      > >>> >> >> >>interop endpoint at
                                                      http://www.whitemesa.net/interop/std.
                                                      > >>> >> >> >>
                                                      > >>> >> >> >>If you could be convinced to get a SOAP-RP endpoint
                                                      running, interop testing
                                                      > >>> >> >> >>using multiple hop routing would be possible. A SOAP-RP
                                                      endpoint is
                                                      > >>> >> >> >>available at WM also [2], with schema and WSDL
                                                      definitions for the test
                                                      > >>> >> >> >>service also available. Unfortunately, no other nodes
                                                      exist at the moment
                                                      > >>> >> >> >>for proper testing.
                                                      > >>> >> >> >>
                                                      > >>> >> >> >>You may be right about toolkits in general. The WM
                                                      server, because of the
                                                      > >>> >> >> >>circumstances of its origin, had to have intermediary
                                                      support baked in early
                                                      > >>> >> >> >>for gateway duties.
                                                      > >>> >> >> >>
                                                      > >>> >> >> >>I hope that more intermediary nodes can be brought up
                                                      for interop testing in
                                                      > >>> >> >> >>the near future. This is a very interesting area.
                                                      > >>> >> >> >>
                                                      > >>> >> >> >>Thanks,
                                                      > >>> >> >> >>
                                                      > >>> >> >> >>RC
                                                      > >>> >> >> >>
                                                      > >>> >> >> >>[1]
                                                      http://www.whitemesa.net/std/relay/interop_relay_index.htm
                                                      > >>> >> >> >>[2] http://www.whitemesa.com/wmsoapsvc_rp.htm
                                                      > >>> >> >> >>
                                                      > >>> >> >> >>> As an experiment in building SOAP intermediaries, i
                                                      put together a
                                                      > >>> >> >> >>> simple intermediary that does request/response
                                                      logging, and a log
                                                      > >>> >> >> >>> viewer.
                                                      > >>> >> >> >>>
                                                      > >>> >> >> >>> There's a request Header that indicates the next hop
                                                      that the request
                                                      > >>> >> >> >>> should be sent to [this should probably be moved to
                                                      SOAP-RP], and the
                                                      > >>> >> >> >>> response contains a header with the link to the
                                                      viewer page for that
                                                      > >>> >> >> >>> capture.
                                                      > >>> >> >> >>>
                                                      > >>> >> >> >>> Here's an example request/response with the headers
                                                      populated
                                                      > >>> >> >> >>> <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://schemas.pocketsoap.com/log/2001/01/'
                                                      > >>> >> >> >>> 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:Log
                                                      S:actor='http://schemas.pocketsoap.com/log/2001/01/'>
                                                      > >>> >> >> >>> <a:NextHop>http://mayhem/ilab/soap.asp</a:NextHop>
                                                      > >>> >> >> >>> </a:Log>
                                                      > >>> >> >> >>> </S:Header>
                                                      > >>> >> >> >>> <S:Body><d:echoString>
                                                      > >>> >> >> >>> <inputString b:type='c:string'>Hello World !
                                                      </inputString>
                                                      > >>> >> >> >>> </d:echoString>
                                                      > >>> >> >> >>> </S:Body></S:Envelope>
                                                      > >>> >> >> >>>
                                                      > >>> >> >> >>> <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/">
                                                      > >>> >> >> >>> <sp:Header
                                                      xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/">
                                                      > >>> >> >> >>> <lg:logResults
                                                      > >>> >> >> >>>
                                                      > >>> >> >>
                                                      >>xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/">http://63.202.
                                                      173.234:
                                                      > >>> >> >> >>81/logViewer.aspx?id=9550da03-bf88-425a-87bd-
                                                      286e97fba9eb</lg:logResults>
                                                      > >>> >> >> >>> </sp:Header>
                                                      > >>> >> >> >>> <SOAP-ENV:Body>
                                                      > >>> >> >> >>> <m:echoStringResponse
                                                      xmlns:m="http://soapinterop.org/">
                                                      > >>> >> >> >>> <outputString xsi:type="xsd:string">Hello World !
                                                      </outputString>
                                                      > >>> >> >> >>> </m:echoStringResponse>
                                                      > >>> >> >> >>> </SOAP-ENV:Body></SOAP-ENV:Envelope>
                                                      > >>> >> >> >>>
                                                      > >>> >> >> >>> I'm coming to the conclusion that your average soap
                                                      client/server
                                                      > >>> >> >> >>> toolkit doesn't make a good starting point for
                                                      building
                                                      > >>> >> >> >>> intermediaries, what do you think ?
                                                      > >>> >> >> >>>
                                                      > >>> >> >> >>> The service is up and running at
                                                      http://63.202.173.234:81/log.ashx if
                                                      > >>> >> >> >>> anyone wants to try it out.
                                                      > >>> >> >> >>>
                                                      > >>> >> >> >>> Cheers
                                                      > >>> >> >> >>> Simon
                                                      > >>> >> >> >>> www.pocketsoap.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@y...
                                                      > >>> >> >> >>>
                                                      > >>> >> >> >>>
                                                      > >>> >> >> >>>
                                                      > >>> >> >> >>> 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
                                                      > >>int
                                                      > >>> >eroperability issues. Please stay on-topic.
                                                      > >>> >> >> >>
                                                      > >>> >> >> >>To unsubscribe from this group, send an email to:
                                                      > >>> >> >> >>soapbuilders-unsubscribe@y...
                                                      > >>> >> >> >>
                                                      > >>> >> >> >>
                                                      > >>> >> >> >>
                                                      > >>> >> >> >>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 i
                                                      > >>nte
                                                      > >>> >roperability issues. Please stay on-topic.
                                                      > >>> >> >> >
                                                      > >>> >> >> >To unsubscribe from this group, send an email to:
                                                      > >>> >> >> >soapbuilders-unsubscribe@y...
                                                      > >>> >> >> >
                                                      > >>> >> >> >
                                                      > >>> >> >> >
                                                      > >>> >> >> >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 in
                                                      > >>ter
                                                      > >>> >operability issues. Please stay on-topic.
                                                      > >>> >> >>
                                                      > >>> >> >> To unsubscribe from this group, send an email to:
                                                      > >>> >> >> soapbuilders-unsubscribe@y...
                                                      > >>> >> >>
                                                      > >>> >> >>
                                                      > >>> >> >>
                                                      > >>> >> >> 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 inte
                                                      > >>rop
                                                      > >>> >erability issues. Please stay on-topic.
                                                      > >>> >> >
                                                      > >>> >> >To unsubscribe from this group, send an email to:
                                                      > >>> >> >soapbuilders-unsubscribe@y...
                                                      > >>> >> >
                                                      > >>> >> >
                                                      > >>> >> >
                                                      > >>> >> >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 inter
                                                      > >>ope
                                                      > >>> >rability issues. Please stay on-topic.
                                                      > >>> >>
                                                      > >>> >> To unsubscribe from this group, send an email to:
                                                      > >>> >> soapbuilders-unsubscribe@y...
                                                      > >>> >>
                                                      > >>> >>
                                                      > >>> >>
                                                      > >>> >> 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 interop
                                                      > >>erability issues. Please stay on-topic.
                                                      > >>> >
                                                      > >>> >To unsubscribe from this group, send an email to:
                                                      > >>> >soapbuilders-unsubscribe@y...
                                                      > >>> >
                                                      > >>> >
                                                      > >>> >
                                                      > >>> >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 interope
                                                      > >>rability issues. Please stay on-topic.
                                                      > >>>
                                                      > >>> To unsubscribe from this group, send an email to:
                                                      > >>> soapbuilders-unsubscribe@y...
                                                      > >>>
                                                      > >>>
                                                      > >>>
                                                      > >>> 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@y...
                                                      > >>
                                                      > >>
                                                      > >>
                                                      > >>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@y...
                                                      > >
                                                      > >
                                                      > >
                                                      > >Your use of Yahoo! Groups is subject to
                                                      http://docs.yahoo.com/info/terms/
                                                      > >
                                                    • Simon Fell
                                                      The problem is that the response from the final destination doesn t have a SOAP-RP header in it. The final destination also has to support SOAP-RP. Cheers
                                                      Message 26 of 28 , Nov 3, 2001
                                                      • 0 Attachment
                                                        The problem is that the response from the final destination doesn't
                                                        have a SOAP-RP header in it. The final destination also has to support
                                                        SOAP-RP.

                                                        Cheers
                                                        Simon

                                                        On Sun, 04 Nov 2001 01:55:58 -0000, in soap you wrote:

                                                        >Hi Simon,
                                                        >
                                                        >When I sent the following message to log-rp.ashx:
                                                        >
                                                        >
                                                        ><?xml version="1.0" encoding="UTF-8" standalone="no"?>
                                                        ><SOAP-ENV:Envelope xmlns:SOAP-
                                                        >ENV="http://schemas.xmlsoap.org/soap/envelope/"
                                                        >xmlns:tns="http://www.xmethods.net/sd/TemperatureService.wsdl"
                                                        >xmlns:xsd="http://www.w3.org/1999/XMLSchema"
                                                        >xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
                                                        >xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:SOAP-
                                                        >ENC="http://schemas.xmlsoap.org/soap/encoding/" SOAP-
                                                        >ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-
                                                        >ENV:Header><mm:path xmlns:mm="http://schemas.xmlsoap.org/rp/" SOAP-
                                                        >ENV:actor="http://schemas.xmlsoap.org/soap/actor/next" SOAP-
                                                        >ENV:mustUnderstand="1"><mm:action></mm:action><mm:to>http://services.x
                                                        >methods.net:80/soap/servlet/rpcrouter</mm:to><mm:id>5efd520d-d0c4-
                                                        >11d5-8fe6-
                                                        >00105a24f6d1</mm:id><mm:fwd><mm:via>http://63.202.173.234:81/log-
                                                        >rp.ashx</mm:via></mm:fwd><mm:rev><mm:via/></mm:rev></mm:path></SOAP-
                                                        >ENV:Header> <SOAP-ENV:Body><mns:getTemp xmlns:mns="urn:xmethods-
                                                        >Temperature"><zipcode
                                                        >xsi:type="xsd:string">20876</zipcode></mns:getTemp></SOAP-ENV:Body>
                                                        ></SOAP-ENV:Envelope>
                                                        >
                                                        >I got a fault message back,
                                                        >
                                                        ><sp:Envelope
                                                        >xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/"><sp:Body><sp:Faul
                                                        >t><faultcode>sp:Client</faultcode><faultstring>Value null was found
                                                        >where an instance of an object was
                                                        >required.</faultstring><faultactor>http://schemas.pocketsoap.com/log/2
                                                        >001/01/</faultactor><detail><lg:StackTrace
                                                        >xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/"> at
                                                        >logiRP.InboundRPProcessing(XmlNode rpNode) in C:\soap\dotnetsoap\log-
                                                        >rp.ashx:line 149
                                                        >
                                                        > at logiRP.ProcessRequest(HttpContext context) in
                                                        >C:\soap\dotnetsoap\log-rp.ashx:line
                                                        >60</lg:StackTrace></detail></sp:Fault></sp:Body></sp:Envelope>
                                                        >
                                                        >
                                                        >Any idea what's wong in the request?
                                                        >
                                                        >Thanks!
                                                        >
                                                        >Yunhao
                                                        >
                                                        >
                                                        >
                                                        >
                                                        >--- In soapbuilders@y..., Simon Fell <soap@z...> wrote:
                                                        >> Bob, you're correct [of course !], I've updated my endpoint
                                                        >> accordingly.
                                                        >>
                                                        >> Cheers
                                                        >> Simon
                                                        >> www.pocketsoap.com
                                                        >>
                                                        >> On Tue, 30 Oct 2001 14:07:39 -0800, in soap you wrote:
                                                        >>
                                                        >> >Hi Bob,
                                                        >> >
                                                        >> >I'll have to read the spec again, i thought the via elements were
                                                        >for
                                                        >> >intermediaries, therefore the server shouldn't enter one in the
                                                        >> >reverse path.
                                                        >> >
                                                        >> >Cheers
                                                        >> >Simon
                                                        >> >
                                                        >> >On Tue, 30 Oct 2001 14:35:27 -0700, in soap you wrote:
                                                        >> >
                                                        >> >>Hi Simon,
                                                        >> >>
                                                        >> >>I notice that your RP endpoint doesn't make an entry in the "rev"
                                                        >> >>reverse path element it includes in the response message
                                                        >(no "via"
                                                        >> >>child element is present). Is this intentional? Although the
                                                        >reverse
                                                        >> >>path element is optional, I believe that if it *is* present, each
                                                        >node
                                                        >> >>is expected to insert a "via" element into it, including the
                                                        >sender.
                                                        >> >>
                                                        >> >>What's happening is that if the WM intermediaries see a "rev"
                                                        >> >>element in the response, they insert a "via" element into it. But
                                                        >the
                                                        >> >>result is an incomplete reverse path, since it lacks the
                                                        >endpoint's
                                                        >> >>URL. This might be worse than having no reverse path at all.
                                                        >> >>
                                                        >> >>What do you think?
                                                        >> >>
                                                        >> >>RC
                                                        >> >>
                                                        >> >>
                                                        >> >>> Cool :)
                                                        >> >>>
                                                        >> >>> There's a SOAP-RP version of the logging intermediary at
                                                        >> >>> http://63.202.173.234:81/log-rp.ashx
                                                        >> >>>
                                                        >> >>> Cheers
                                                        >> >>> Simon
                                                        >> >>>
                                                        >> >>> On Tue, 30 Oct 2001 11:31:20 -0700, in soap you wrote:
                                                        >> >>>
                                                        >> >>> >Hi Simon,
                                                        >> >>> >
                                                        >> >>> >Success! I've been able to route a request through one or both
                                                        >of
                                                        >> >>> >the 2 WM nodes to your endpoint. Does your intermediary node
                                                        >> >>> >support RP yet?
                                                        >> >>> >
                                                        >> >>> >Thanks,
                                                        >> >>> >
                                                        >> >>> >RC
                                                        >> >>> >
                                                        >> >>> >> Good point, I've updated it to set both the actor and
                                                        >mustUnderstand
                                                        >> >>> >> in the response.
                                                        >> >>> >>
                                                        >> >>> >> Cheers
                                                        >> >>> >> Simon
                                                        >> >>> >>
                                                        >> >>> >> On Tue, 30 Oct 2001 01:16:27 -0700, in soap you wrote:
                                                        >> >>> >>
                                                        >> >>> >> >Hi Simon,
                                                        >> >>> >> >
                                                        >> >>> >> >Ok, when trying to use the WM intermediary, there's a
                                                        >problem... it's not happy because the 4s4c SOAP-RP endpoint isn't
                                                        >placing an "actor" attribute on the header entry it places in the
                                                        >*response* message, and the WM intermediary expects to
                                                        >find "http://schemas.xmlsoap.org/soap/actor/next"
                                                        >> >>at
                                                        >> >>> >a minimum. You might have noticed that the WM endpoint does
                                                        >this with SOAP-RP headers in the response. With none specified at
                                                        >all, and it being aware that it's not the "default actor", the
                                                        >intermediary thinks that it is not the target of the header entry.
                                                        >It's always seemed to me that headers
                                                        >> >>in
                                                        >> >>> >response messages need to specify their target, no differently
                                                        >than those in request messages, for all the same reasons. If there
                                                        >are multiple intermediaries in the path, how would header entries in
                                                        >the response message get processed correctly without targeting them
                                                        >at the proper actor (which
                                                        >> >>> >might be associated with only one of possibly many nodes in
                                                        >the path)? Of course a routing header is most
                                                        >> >>> >> >conveniently handled by using actor "next", for obvious
                                                        >reasons. This issue doesn't even exist until you start using
                                                        >intermediaries.
                                                        >> >>> >> >
                                                        >> >>> >> >What do you think??
                                                        >> >>> >> >
                                                        >> >>> >> >Anyway, looking at the wire dumps, everything is fine,
                                                        >other than this.
                                                        >> >>> >> >
                                                        >> >>> >> >RC
                                                        >> >>> >> >
                                                        >> >>> >> >> Assuming you can get a connection, there's a SOAP-RP
                                                        >enabled version
                                                        >> >>> >> >> of the interop endpoint running at
                                                        >> >>> >> >> http://63.202.173.234:81/ilab-rp.ashx
                                                        >> >>> >> >>
                                                        >> >>> >> >> All the SOAP-RP error handling isn't in place yet, but
                                                        >the basics
                                                        >> >>> >> >> should work fine.
                                                        >> >>> >> >>
                                                        >> >>> >> >> Cheers
                                                        >> >>> >> >> Simon
                                                        >> >>> >> >>
                                                        >> >>> >> >> On Mon, 29 Oct 2001 09:04:21 -0800, in soap you wrote:
                                                        >> >>> >> >>
                                                        >> >>> >> >> >I have a SOAP-RP enabled version of the logger running
                                                        >at
                                                        >> >>> >> >> >http://63.202.173.234:81/log-rp.ashx which i've been
                                                        >testing in
                                                        >> >>> >> >> >conjunction with the White Mesa SOAP-RP enabled endpoint.
                                                        >> >>> >> >> >
                                                        >> >>> >> >> >I'll try and get a SOAP-RP enabled endpoint up and
                                                        >running as well.
                                                        >> >>> >> >> >
                                                        >> >>> >> >> >Cheers
                                                        >> >>> >> >> >Simon
                                                        >> >>> >> >> >www.pocketsoap.com
                                                        >> >>> >> >> >
                                                        >> >>> >> >> >
                                                        >> >>> >> >> >On Sun, 28 Oct 2001 07:16:53 -0700, in soap you wrote:
                                                        >> >>> >> >> >
                                                        >> >>> >> >> >>Hi Simon,
                                                        >> >>> >> >> >>
                                                        >> >>> >> >> >>Looks good, I'll give it a shot when I get a chance. A
                                                        >similar thing is
                                                        >> >>> >> >> >>available at the White Mesa site [1]. This is supported
                                                        >by the normal
                                                        >> >>> >> >> >>interop endpoint at
                                                        >http://www.whitemesa.net/interop/std.
                                                        >> >>> >> >> >>
                                                        >> >>> >> >> >>If you could be convinced to get a SOAP-RP endpoint
                                                        >running, interop testing
                                                        >> >>> >> >> >>using multiple hop routing would be possible. A SOAP-RP
                                                        >endpoint is
                                                        >> >>> >> >> >>available at WM also [2], with schema and WSDL
                                                        >definitions for the test
                                                        >> >>> >> >> >>service also available. Unfortunately, no other nodes
                                                        >exist at the moment
                                                        >> >>> >> >> >>for proper testing.
                                                        >> >>> >> >> >>
                                                        >> >>> >> >> >>You may be right about toolkits in general. The WM
                                                        >server, because of the
                                                        >> >>> >> >> >>circumstances of its origin, had to have intermediary
                                                        >support baked in early
                                                        >> >>> >> >> >>for gateway duties.
                                                        >> >>> >> >> >>
                                                        >> >>> >> >> >>I hope that more intermediary nodes can be brought up
                                                        >for interop testing in
                                                        >> >>> >> >> >>the near future. This is a very interesting area.
                                                        >> >>> >> >> >>
                                                        >> >>> >> >> >>Thanks,
                                                        >> >>> >> >> >>
                                                        >> >>> >> >> >>RC
                                                        >> >>> >> >> >>
                                                        >> >>> >> >> >>[1]
                                                        >http://www.whitemesa.net/std/relay/interop_relay_index.htm
                                                        >> >>> >> >> >>[2] http://www.whitemesa.com/wmsoapsvc_rp.htm
                                                        >> >>> >> >> >>
                                                        >> >>> >> >> >>> As an experiment in building SOAP intermediaries, i
                                                        >put together a
                                                        >> >>> >> >> >>> simple intermediary that does request/response
                                                        >logging, and a log
                                                        >> >>> >> >> >>> viewer.
                                                        >> >>> >> >> >>>
                                                        >> >>> >> >> >>> There's a request Header that indicates the next hop
                                                        >that the request
                                                        >> >>> >> >> >>> should be sent to [this should probably be moved to
                                                        >SOAP-RP], and the
                                                        >> >>> >> >> >>> response contains a header with the link to the
                                                        >viewer page for that
                                                        >> >>> >> >> >>> capture.
                                                        >> >>> >> >> >>>
                                                        >> >>> >> >> >>> Here's an example request/response with the headers
                                                        >populated
                                                        >> >>> >> >> >>> <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://schemas.pocketsoap.com/log/2001/01/'
                                                        >> >>> >> >> >>> 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:Log
                                                        >S:actor='http://schemas.pocketsoap.com/log/2001/01/'>
                                                        >> >>> >> >> >>> <a:NextHop>http://mayhem/ilab/soap.asp</a:NextHop>
                                                        >> >>> >> >> >>> </a:Log>
                                                        >> >>> >> >> >>> </S:Header>
                                                        >> >>> >> >> >>> <S:Body><d:echoString>
                                                        >> >>> >> >> >>> <inputString b:type='c:string'>Hello World !
                                                        ></inputString>
                                                        >> >>> >> >> >>> </d:echoString>
                                                        >> >>> >> >> >>> </S:Body></S:Envelope>
                                                        >> >>> >> >> >>>
                                                        >> >>> >> >> >>> <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/">
                                                        >> >>> >> >> >>> <sp:Header
                                                        >xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/">
                                                        >> >>> >> >> >>> <lg:logResults
                                                        >> >>> >> >> >>>
                                                        >> >>> >> >>
                                                        >>>xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/">http://63.202.
                                                        >173.234:
                                                        >> >>> >> >> >>81/logViewer.aspx?id=9550da03-bf88-425a-87bd-
                                                        >286e97fba9eb</lg:logResults>
                                                        >> >>> >> >> >>> </sp:Header>
                                                        >> >>> >> >> >>> <SOAP-ENV:Body>
                                                        >> >>> >> >> >>> <m:echoStringResponse
                                                        >xmlns:m="http://soapinterop.org/">
                                                        >> >>> >> >> >>> <outputString xsi:type="xsd:string">Hello World !
                                                        ></outputString>
                                                        >> >>> >> >> >>> </m:echoStringResponse>
                                                        >> >>> >> >> >>> </SOAP-ENV:Body></SOAP-ENV:Envelope>
                                                        >> >>> >> >> >>>
                                                        >> >>> >> >> >>> I'm coming to the conclusion that your average soap
                                                        >client/server
                                                        >> >>> >> >> >>> toolkit doesn't make a good starting point for
                                                        >building
                                                        >> >>> >> >> >>> intermediaries, what do you think ?
                                                        >> >>> >> >> >>>
                                                        >> >>> >> >> >>> The service is up and running at
                                                        >http://63.202.173.234:81/log.ashx if
                                                        >> >>> >> >> >>> anyone wants to try it out.
                                                        >> >>> >> >> >>>
                                                        >> >>> >> >> >>> Cheers
                                                        >> >>> >> >> >>> Simon
                                                        >> >>> >> >> >>> www.pocketsoap.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@y...
                                                        >> >>> >> >> >>>
                                                        >> >>> >> >> >>>
                                                        >> >>> >> >> >>>
                                                        >> >>> >> >> >>> 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
                                                        >> >>int
                                                        >> >>> >eroperability issues. Please stay on-topic.
                                                        >> >>> >> >> >>
                                                        >> >>> >> >> >>To unsubscribe from this group, send an email to:
                                                        >> >>> >> >> >>soapbuilders-unsubscribe@y...
                                                        >> >>> >> >> >>
                                                        >> >>> >> >> >>
                                                        >> >>> >> >> >>
                                                        >> >>> >> >> >>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 i
                                                        >> >>nte
                                                        >> >>> >roperability issues. Please stay on-topic.
                                                        >> >>> >> >> >
                                                        >> >>> >> >> >To unsubscribe from this group, send an email to:
                                                        >> >>> >> >> >soapbuilders-unsubscribe@y...
                                                        >> >>> >> >> >
                                                        >> >>> >> >> >
                                                        >> >>> >> >> >
                                                        >> >>> >> >> >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 in
                                                        >> >>ter
                                                        >> >>> >operability issues. Please stay on-topic.
                                                        >> >>> >> >>
                                                        >> >>> >> >> To unsubscribe from this group, send an email to:
                                                        >> >>> >> >> soapbuilders-unsubscribe@y...
                                                        >> >>> >> >>
                                                        >> >>> >> >>
                                                        >> >>> >> >>
                                                        >> >>> >> >> 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 inte
                                                        >> >>rop
                                                        >> >>> >erability issues. Please stay on-topic.
                                                        >> >>> >> >
                                                        >> >>> >> >To unsubscribe from this group, send an email to:
                                                        >> >>> >> >soapbuilders-unsubscribe@y...
                                                        >> >>> >> >
                                                        >> >>> >> >
                                                        >> >>> >> >
                                                        >> >>> >> >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 inter
                                                        >> >>ope
                                                        >> >>> >rability issues. Please stay on-topic.
                                                        >> >>> >>
                                                        >> >>> >> To unsubscribe from this group, send an email to:
                                                        >> >>> >> soapbuilders-unsubscribe@y...
                                                        >> >>> >>
                                                        >> >>> >>
                                                        >> >>> >>
                                                        >> >>> >> Your use of Yahoo! Groups is subject to
                                                        >http://docs.yahoo.com/info/terms/
                                                        >> >>> >>
                                                        >> >>> >
                                                        >> >>> >
                                                        >> >>> >
                                                        >> >>> >---------------------------------------------------------------
                                                      • yzhang@motherbot.com
                                                        Thanks, Simon! I really hoped the final targets won t need to when use a request/response protocal. So that they can concentrate on building services, and
                                                        Message 27 of 28 , Nov 3, 2001
                                                        • 0 Attachment
                                                          Thanks, Simon! I really hoped the final targets won't need to when
                                                          use a request/response protocal. So that they can concentrate on
                                                          building services, and aren't worry about routing at all. A logging
                                                          intermediary based on SOAP-RP would fail in most of the situations,
                                                          huh?

                                                          Cheers,

                                                          Yunhao



                                                          --- In soapbuilders@y..., Simon Fell <soap@z...> wrote:
                                                          > The problem is that the response from the final destination doesn't
                                                          > have a SOAP-RP header in it. The final destination also has to
                                                          support
                                                          > SOAP-RP.
                                                          >
                                                          > Cheers
                                                          > Simon
                                                          >
                                                          > On Sun, 04 Nov 2001 01:55:58 -0000, in soap you wrote:
                                                          >
                                                          > >Hi Simon,
                                                          > >
                                                          > >When I sent the following message to log-rp.ashx:
                                                          > >
                                                          > >
                                                          > ><?xml version="1.0" encoding="UTF-8" standalone="no"?>
                                                          > ><SOAP-ENV:Envelope xmlns:SOAP-
                                                          > >ENV="http://schemas.xmlsoap.org/soap/envelope/"
                                                          > >xmlns:tns="http://www.xmethods.net/sd/TemperatureService.wsdl"
                                                          > >xmlns:xsd="http://www.w3.org/1999/XMLSchema"
                                                          > >xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
                                                          > >xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:SOAP-
                                                          > >ENC="http://schemas.xmlsoap.org/soap/encoding/" SOAP-
                                                          >
                                                          >ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-
                                                          > >ENV:Header><mm:path xmlns:mm="http://schemas.xmlsoap.org/rp/" SOAP-
                                                          > >ENV:actor="http://schemas.xmlsoap.org/soap/actor/next" SOAP-
                                                          >
                                                          >ENV:mustUnderstand="1"><mm:action></mm:action><mm:to>http://services.
                                                          x
                                                          > >methods.net:80/soap/servlet/rpcrouter</mm:to><mm:id>5efd520d-d0c4-
                                                          > >11d5-8fe6-
                                                          > >00105a24f6d1</mm:id><mm:fwd><mm:via>http://63.202.173.234:81/log-
                                                          >
                                                          >rp.ashx</mm:via></mm:fwd><mm:rev><mm:via/></mm:rev></mm:path></SOAP-
                                                          > >ENV:Header> <SOAP-ENV:Body><mns:getTemp xmlns:mns="urn:xmethods-
                                                          > >Temperature"><zipcode
                                                          > >xsi:type="xsd:string">20876</zipcode></mns:getTemp></SOAP-
                                                          ENV:Body>
                                                          > ></SOAP-ENV:Envelope>
                                                          > >
                                                          > >I got a fault message back,
                                                          > >
                                                          > ><sp:Envelope
                                                          >
                                                          >xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/"><sp:Body><sp:Fau
                                                          l
                                                          > >t><faultcode>sp:Client</faultcode><faultstring>Value null was
                                                          found
                                                          > >where an instance of an object was
                                                          >
                                                          >required.</faultstring><faultactor>http://schemas.pocketsoap.com/log/
                                                          2
                                                          > >001/01/</faultactor><detail><lg:StackTrace
                                                          > >xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/"> at
                                                          > >logiRP.InboundRPProcessing(XmlNode rpNode) in
                                                          C:\soap\dotnetsoap\log-
                                                          > >rp.ashx:line 149
                                                          > >
                                                          > > at logiRP.ProcessRequest(HttpContext context) in
                                                          > >C:\soap\dotnetsoap\log-rp.ashx:line
                                                          > >60</lg:StackTrace></detail></sp:Fault></sp:Body></sp:Envelope>
                                                          > >
                                                          > >
                                                          > >Any idea what's wong in the request?
                                                          > >
                                                          > >Thanks!
                                                          > >
                                                          > >Yunhao
                                                          > >
                                                          > >
                                                          > >
                                                          > >
                                                          > >--- In soapbuilders@y..., Simon Fell <soap@z...> wrote:
                                                          > >> Bob, you're correct [of course !], I've updated my endpoint
                                                          > >> accordingly.
                                                          > >>
                                                          > >> Cheers
                                                          > >> Simon
                                                          > >> www.pocketsoap.com
                                                          > >>
                                                          > >> On Tue, 30 Oct 2001 14:07:39 -0800, in soap you wrote:
                                                          > >>
                                                          > >> >Hi Bob,
                                                          > >> >
                                                          > >> >I'll have to read the spec again, i thought the via elements
                                                          were
                                                          > >for
                                                          > >> >intermediaries, therefore the server shouldn't enter one in the
                                                          > >> >reverse path.
                                                          > >> >
                                                          > >> >Cheers
                                                          > >> >Simon
                                                          > >> >
                                                          > >> >On Tue, 30 Oct 2001 14:35:27 -0700, in soap you wrote:
                                                          > >> >
                                                          > >> >>Hi Simon,
                                                          > >> >>
                                                          > >> >>I notice that your RP endpoint doesn't make an entry in
                                                          the "rev"
                                                          > >> >>reverse path element it includes in the response message
                                                          > >(no "via"
                                                          > >> >>child element is present). Is this intentional? Although the
                                                          > >reverse
                                                          > >> >>path element is optional, I believe that if it *is* present,
                                                          each
                                                          > >node
                                                          > >> >>is expected to insert a "via" element into it, including the
                                                          > >sender.
                                                          > >> >>
                                                          > >> >>What's happening is that if the WM intermediaries see a "rev"
                                                          > >> >>element in the response, they insert a "via" element into it.
                                                          But
                                                          > >the
                                                          > >> >>result is an incomplete reverse path, since it lacks the
                                                          > >endpoint's
                                                          > >> >>URL. This might be worse than having no reverse path at all.
                                                          > >> >>
                                                          > >> >>What do you think?
                                                          > >> >>
                                                          > >> >>RC
                                                          > >> >>
                                                          > >> >>
                                                          > >> >>> Cool :)
                                                          > >> >>>
                                                          > >> >>> There's a SOAP-RP version of the logging intermediary at
                                                          > >> >>> http://63.202.173.234:81/log-rp.ashx
                                                          > >> >>>
                                                          > >> >>> Cheers
                                                          > >> >>> Simon
                                                          > >> >>>
                                                          > >> >>> On Tue, 30 Oct 2001 11:31:20 -0700, in soap you wrote:
                                                          > >> >>>
                                                          > >> >>> >Hi Simon,
                                                          > >> >>> >
                                                          > >> >>> >Success! I've been able to route a request through one or
                                                          both
                                                          > >of
                                                          > >> >>> >the 2 WM nodes to your endpoint. Does your intermediary
                                                          node
                                                          > >> >>> >support RP yet?
                                                          > >> >>> >
                                                          > >> >>> >Thanks,
                                                          > >> >>> >
                                                          > >> >>> >RC
                                                          > >> >>> >
                                                          > >> >>> >> Good point, I've updated it to set both the actor and
                                                          > >mustUnderstand
                                                          > >> >>> >> in the response.
                                                          > >> >>> >>
                                                          > >> >>> >> Cheers
                                                          > >> >>> >> Simon
                                                          > >> >>> >>
                                                          > >> >>> >> On Tue, 30 Oct 2001 01:16:27 -0700, in soap you wrote:
                                                          > >> >>> >>
                                                          > >> >>> >> >Hi Simon,
                                                          > >> >>> >> >
                                                          > >> >>> >> >Ok, when trying to use the WM intermediary, there's a
                                                          > >problem... it's not happy because the 4s4c SOAP-RP endpoint isn't
                                                          > >placing an "actor" attribute on the header entry it places in the
                                                          > >*response* message, and the WM intermediary expects to
                                                          > >find "http://schemas.xmlsoap.org/soap/actor/next"
                                                          > >> >>at
                                                          > >> >>> >a minimum. You might have noticed that the WM endpoint does
                                                          > >this with SOAP-RP headers in the response. With none specified at
                                                          > >all, and it being aware that it's not the "default actor", the
                                                          > >intermediary thinks that it is not the target of the header entry.
                                                          > >It's always seemed to me that headers
                                                          > >> >>in
                                                          > >> >>> >response messages need to specify their target, no
                                                          differently
                                                          > >than those in request messages, for all the same reasons. If there
                                                          > >are multiple intermediaries in the path, how would header entries
                                                          in
                                                          > >the response message get processed correctly without targeting
                                                          them
                                                          > >at the proper actor (which
                                                          > >> >>> >might be associated with only one of possibly many nodes in
                                                          > >the path)? Of course a routing header is most
                                                          > >> >>> >> >conveniently handled by using actor "next", for obvious
                                                          > >reasons. This issue doesn't even exist until you start using
                                                          > >intermediaries.
                                                          > >> >>> >> >
                                                          > >> >>> >> >What do you think??
                                                          > >> >>> >> >
                                                          > >> >>> >> >Anyway, looking at the wire dumps, everything is fine,
                                                          > >other than this.
                                                          > >> >>> >> >
                                                          > >> >>> >> >RC
                                                          > >> >>> >> >
                                                          > >> >>> >> >> Assuming you can get a connection, there's a SOAP-RP
                                                          > >enabled version
                                                          > >> >>> >> >> of the interop endpoint running at
                                                          > >> >>> >> >> http://63.202.173.234:81/ilab-rp.ashx
                                                          > >> >>> >> >>
                                                          > >> >>> >> >> All the SOAP-RP error handling isn't in place yet, but
                                                          > >the basics
                                                          > >> >>> >> >> should work fine.
                                                          > >> >>> >> >>
                                                          > >> >>> >> >> Cheers
                                                          > >> >>> >> >> Simon
                                                          > >> >>> >> >>
                                                          > >> >>> >> >> On Mon, 29 Oct 2001 09:04:21 -0800, in soap you wrote:
                                                          > >> >>> >> >>
                                                          > >> >>> >> >> >I have a SOAP-RP enabled version of the logger
                                                          running
                                                          > >at
                                                          > >> >>> >> >> >http://63.202.173.234:81/log-rp.ashx which i've been
                                                          > >testing in
                                                          > >> >>> >> >> >conjunction with the White Mesa SOAP-RP enabled
                                                          endpoint.
                                                          > >> >>> >> >> >
                                                          > >> >>> >> >> >I'll try and get a SOAP-RP enabled endpoint up and
                                                          > >running as well.
                                                          > >> >>> >> >> >
                                                          > >> >>> >> >> >Cheers
                                                          > >> >>> >> >> >Simon
                                                          > >> >>> >> >> >www.pocketsoap.com
                                                          > >> >>> >> >> >
                                                          > >> >>> >> >> >
                                                          > >> >>> >> >> >On Sun, 28 Oct 2001 07:16:53 -0700, in soap you wrote:
                                                          > >> >>> >> >> >
                                                          > >> >>> >> >> >>Hi Simon,
                                                          > >> >>> >> >> >>
                                                          > >> >>> >> >> >>Looks good, I'll give it a shot when I get a chance.
                                                          A
                                                          > >similar thing is
                                                          > >> >>> >> >> >>available at the White Mesa site [1]. This is
                                                          supported
                                                          > >by the normal
                                                          > >> >>> >> >> >>interop endpoint at
                                                          > >http://www.whitemesa.net/interop/std.
                                                          > >> >>> >> >> >>
                                                          > >> >>> >> >> >>If you could be convinced to get a SOAP-RP endpoint
                                                          > >running, interop testing
                                                          > >> >>> >> >> >>using multiple hop routing would be possible. A SOAP-
                                                          RP
                                                          > >endpoint is
                                                          > >> >>> >> >> >>available at WM also [2], with schema and WSDL
                                                          > >definitions for the test
                                                          > >> >>> >> >> >>service also available. Unfortunately, no other
                                                          nodes
                                                          > >exist at the moment
                                                          > >> >>> >> >> >>for proper testing.
                                                          > >> >>> >> >> >>
                                                          > >> >>> >> >> >>You may be right about toolkits in general. The WM
                                                          > >server, because of the
                                                          > >> >>> >> >> >>circumstances of its origin, had to have
                                                          intermediary
                                                          > >support baked in early
                                                          > >> >>> >> >> >>for gateway duties.
                                                          > >> >>> >> >> >>
                                                          > >> >>> >> >> >>I hope that more intermediary nodes can be brought
                                                          up
                                                          > >for interop testing in
                                                          > >> >>> >> >> >>the near future. This is a very interesting area.
                                                          > >> >>> >> >> >>
                                                          > >> >>> >> >> >>Thanks,
                                                          > >> >>> >> >> >>
                                                          > >> >>> >> >> >>RC
                                                          > >> >>> >> >> >>
                                                          > >> >>> >> >> >>[1]
                                                          > >http://www.whitemesa.net/std/relay/interop_relay_index.htm
                                                          > >> >>> >> >> >>[2] http://www.whitemesa.com/wmsoapsvc_rp.htm
                                                          > >> >>> >> >> >>
                                                          > >> >>> >> >> >>> As an experiment in building SOAP intermediaries,
                                                          i
                                                          > >put together a
                                                          > >> >>> >> >> >>> simple intermediary that does request/response
                                                          > >logging, and a log
                                                          > >> >>> >> >> >>> viewer.
                                                          > >> >>> >> >> >>>
                                                          > >> >>> >> >> >>> There's a request Header that indicates the next
                                                          hop
                                                          > >that the request
                                                          > >> >>> >> >> >>> should be sent to [this should probably be moved
                                                          to
                                                          > >SOAP-RP], and the
                                                          > >> >>> >> >> >>> response contains a header with the link to the
                                                          > >viewer page for that
                                                          > >> >>> >> >> >>> capture.
                                                          > >> >>> >> >> >>>
                                                          > >> >>> >> >> >>> Here's an example request/response with the
                                                          headers
                                                          > >populated
                                                          > >> >>> >> >> >>> <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://schemas.pocketsoap.com/log/2001/01/'
                                                          > >> >>> >> >> >>> 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:Log
                                                          > >S:actor='http://schemas.pocketsoap.com/log/2001/01/'>
                                                          > >> >>> >> >> >>> <a:NextHop>http://mayhem/ilab/soap.asp</a:NextHop>
                                                          > >> >>> >> >> >>> </a:Log>
                                                          > >> >>> >> >> >>> </S:Header>
                                                          > >> >>> >> >> >>> <S:Body><d:echoString>
                                                          > >> >>> >> >> >>> <inputString b:type='c:string'>Hello World !
                                                          > ></inputString>
                                                          > >> >>> >> >> >>> </d:echoString>
                                                          > >> >>> >> >> >>> </S:Body></S:Envelope>
                                                          > >> >>> >> >> >>>
                                                          > >> >>> >> >> >>> <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/">
                                                          > >> >>> >> >> >>> <sp:Header
                                                          > >xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/">
                                                          > >> >>> >> >> >>> <lg:logResults
                                                          > >> >>> >> >> >>>
                                                          > >> >>> >> >>
                                                          >
                                                          >>>xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/">http://63.202
                                                          .
                                                          > >173.234:
                                                          > >> >>> >> >> >>81/logViewer.aspx?id=9550da03-bf88-425a-87bd-
                                                          > >286e97fba9eb</lg:logResults>
                                                          > >> >>> >> >> >>> </sp:Header>
                                                          > >> >>> >> >> >>> <SOAP-ENV:Body>
                                                          > >> >>> >> >> >>> <m:echoStringResponse
                                                          > >xmlns:m="http://soapinterop.org/">
                                                          > >> >>> >> >> >>> <outputString xsi:type="xsd:string">Hello World !
                                                          > ></outputString>
                                                          > >> >>> >> >> >>> </m:echoStringResponse>
                                                          > >> >>> >> >> >>> </SOAP-ENV:Body></SOAP-ENV:Envelope>
                                                          > >> >>> >> >> >>>
                                                          > >> >>> >> >> >>> I'm coming to the conclusion that your average
                                                          soap
                                                          > >client/server
                                                          > >> >>> >> >> >>> toolkit doesn't make a good starting point for
                                                          > >building
                                                          > >> >>> >> >> >>> intermediaries, what do you think ?
                                                          > >> >>> >> >> >>>
                                                          > >> >>> >> >> >>> The service is up and running at
                                                          > >http://63.202.173.234:81/log.ashx if
                                                          > >> >>> >> >> >>> anyone wants to try it out.
                                                          > >> >>> >> >> >>>
                                                          > >> >>> >> >> >>> Cheers
                                                          > >> >>> >> >> >>> Simon
                                                          > >> >>> >> >> >>> www.pocketsoap.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@y...
                                                          > >> >>> >> >> >>>
                                                          > >> >>> >> >> >>>
                                                          > >> >>> >> >> >>>
                                                          > >> >>> >> >> >>> 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
                                                          > >> >>int
                                                          > >> >>> >eroperability issues. Please stay on-topic.
                                                          > >> >>> >> >> >>
                                                          > >> >>> >> >> >>To unsubscribe from this group, send an email to:
                                                          > >> >>> >> >> >>soapbuilders-unsubscribe@y...
                                                          > >> >>> >> >> >>
                                                          > >> >>> >> >> >>
                                                          > >> >>> >> >> >>
                                                          > >> >>> >> >> >>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 i
                                                          > >> >>nte
                                                          > >> >>> >roperability issues. Please stay on-topic.
                                                          > >> >>> >> >> >
                                                          > >> >>> >> >> >To unsubscribe from this group, send an email to:
                                                          > >> >>> >> >> >soapbuilders-unsubscribe@y...
                                                          > >> >>> >> >> >
                                                          > >> >>> >> >> >
                                                          > >> >>> >> >> >
                                                          > >> >>> >> >> >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 in
                                                          > >> >>ter
                                                          > >> >>> >operability issues. Please stay on-topic.
                                                          > >> >>> >> >>
                                                          > >> >>> >> >> To unsubscribe from this group, send an email to:
                                                          > >> >>> >> >> soapbuilders-unsubscribe@y...
                                                          > >> >>> >> >>
                                                          > >> >>> >> >>
                                                          > >> >>> >> >>
                                                          > >> >>> >> >> 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 inte
                                                          > >> >>rop
                                                          > >> >>> >erability issues. Please stay on-topic.
                                                          > >> >>> >> >
                                                          > >> >>> >> >To unsubscribe from this group, send an email to:
                                                          > >> >>> >> >soapbuilders-unsubscribe@y...
                                                          > >> >>> >> >
                                                          > >> >>> >> >
                                                          > >> >>> >> >
                                                          > >> >>> >> >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 inter
                                                          > >> >>ope
                                                          > >> >>> >rability issues. Please stay on-topic.
                                                          > >> >>> >>
                                                          > >> >>> >> To unsubscribe from this group, send an email to:
                                                          > >> >>> >> soapbuilders-unsubscribe@y...
                                                          > >> >>> >>
                                                          > >> >>> >>
                                                          > >> >>> >>
                                                          > >> >>> >> Your use of Yahoo! Groups is subject to
                                                          > >http://docs.yahoo.com/info/terms/
                                                          > >> >>> >>
                                                          > >> >>> >
                                                          > >> >>> >
                                                          > >> >>> >
                                                          > >> >>> >------------------------------------------------------------
                                                          ---
                                                        • Simon Fell
                                                          yes, there s a non SOAP-RP version available as well, see http://groups.yahoo.com/group/soapbuilders/message/5756 Cheers Simon
                                                          Message 28 of 28 , Nov 3, 2001
                                                          • 0 Attachment
                                                            yes, there's a non SOAP-RP version available as well, see
                                                            http://groups.yahoo.com/group/soapbuilders/message/5756

                                                            Cheers
                                                            Simon

                                                            On Sun, 04 Nov 2001 03:09:35 -0000, in soap you wrote:

                                                            >Thanks, Simon! I really hoped the final targets won't need to when
                                                            >use a request/response protocal. So that they can concentrate on
                                                            >building services, and aren't worry about routing at all. A logging
                                                            >intermediary based on SOAP-RP would fail in most of the situations,
                                                            >huh?
                                                            >
                                                            >Cheers,
                                                            >
                                                            >Yunhao
                                                            >
                                                            >
                                                            >
                                                            >--- In soapbuilders@y..., Simon Fell <soap@z...> wrote:
                                                            >> The problem is that the response from the final destination doesn't
                                                            >> have a SOAP-RP header in it. The final destination also has to
                                                            >support
                                                            >> SOAP-RP.
                                                            >>
                                                            >> Cheers
                                                            >> Simon
                                                            >>
                                                            >> On Sun, 04 Nov 2001 01:55:58 -0000, in soap you wrote:
                                                            >>
                                                            >> >Hi Simon,
                                                            >> >
                                                            >> >When I sent the following message to log-rp.ashx:
                                                            >> >
                                                            >> >
                                                            >> ><?xml version="1.0" encoding="UTF-8" standalone="no"?>
                                                            >> ><SOAP-ENV:Envelope xmlns:SOAP-
                                                            >> >ENV="http://schemas.xmlsoap.org/soap/envelope/"
                                                            >> >xmlns:tns="http://www.xmethods.net/sd/TemperatureService.wsdl"
                                                            >> >xmlns:xsd="http://www.w3.org/1999/XMLSchema"
                                                            >> >xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
                                                            >> >xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:SOAP-
                                                            >> >ENC="http://schemas.xmlsoap.org/soap/encoding/" SOAP-
                                                            >>
                                                            >>ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-
                                                            >> >ENV:Header><mm:path xmlns:mm="http://schemas.xmlsoap.org/rp/" SOAP-
                                                            >> >ENV:actor="http://schemas.xmlsoap.org/soap/actor/next" SOAP-
                                                            >>
                                                            >>ENV:mustUnderstand="1"><mm:action></mm:action><mm:to>http://services.
                                                            >x
                                                            >> >methods.net:80/soap/servlet/rpcrouter</mm:to><mm:id>5efd520d-d0c4-
                                                            >> >11d5-8fe6-
                                                            >> >00105a24f6d1</mm:id><mm:fwd><mm:via>http://63.202.173.234:81/log-
                                                            >>
                                                            >>rp.ashx</mm:via></mm:fwd><mm:rev><mm:via/></mm:rev></mm:path></SOAP-
                                                            >> >ENV:Header> <SOAP-ENV:Body><mns:getTemp xmlns:mns="urn:xmethods-
                                                            >> >Temperature"><zipcode
                                                            >> >xsi:type="xsd:string">20876</zipcode></mns:getTemp></SOAP-
                                                            >ENV:Body>
                                                            >> ></SOAP-ENV:Envelope>
                                                            >> >
                                                            >> >I got a fault message back,
                                                            >> >
                                                            >> ><sp:Envelope
                                                            >>
                                                            >>xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/"><sp:Body><sp:Fau
                                                            >l
                                                            >> >t><faultcode>sp:Client</faultcode><faultstring>Value null was
                                                            >found
                                                            >> >where an instance of an object was
                                                            >>
                                                            >>required.</faultstring><faultactor>http://schemas.pocketsoap.com/log/
                                                            >2
                                                            >> >001/01/</faultactor><detail><lg:StackTrace
                                                            >> >xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/"> at
                                                            >> >logiRP.InboundRPProcessing(XmlNode rpNode) in
                                                            >C:\soap\dotnetsoap\log-
                                                            >> >rp.ashx:line 149
                                                            >> >
                                                            >> > at logiRP.ProcessRequest(HttpContext context) in
                                                            >> >C:\soap\dotnetsoap\log-rp.ashx:line
                                                            >> >60</lg:StackTrace></detail></sp:Fault></sp:Body></sp:Envelope>
                                                            >> >
                                                            >> >
                                                            >> >Any idea what's wong in the request?
                                                            >> >
                                                            >> >Thanks!
                                                            >> >
                                                            >> >Yunhao
                                                            >> >
                                                            >> >
                                                            >> >
                                                            >> >
                                                            >> >--- In soapbuilders@y..., Simon Fell <soap@z...> wrote:
                                                            >> >> Bob, you're correct [of course !], I've updated my endpoint
                                                            >> >> accordingly.
                                                            >> >>
                                                            >> >> Cheers
                                                            >> >> Simon
                                                            >> >> www.pocketsoap.com
                                                            >> >>
                                                            >> >> On Tue, 30 Oct 2001 14:07:39 -0800, in soap you wrote:
                                                            >> >>
                                                            >> >> >Hi Bob,
                                                            >> >> >
                                                            >> >> >I'll have to read the spec again, i thought the via elements
                                                            >were
                                                            >> >for
                                                            >> >> >intermediaries, therefore the server shouldn't enter one in the
                                                            >> >> >reverse path.
                                                            >> >> >
                                                            >> >> >Cheers
                                                            >> >> >Simon
                                                            >> >> >
                                                            >> >> >On Tue, 30 Oct 2001 14:35:27 -0700, in soap you wrote:
                                                            >> >> >
                                                            >> >> >>Hi Simon,
                                                            >> >> >>
                                                            >> >> >>I notice that your RP endpoint doesn't make an entry in
                                                            >the "rev"
                                                            >> >> >>reverse path element it includes in the response message
                                                            >> >(no "via"
                                                            >> >> >>child element is present). Is this intentional? Although the
                                                            >> >reverse
                                                            >> >> >>path element is optional, I believe that if it *is* present,
                                                            >each
                                                            >> >node
                                                            >> >> >>is expected to insert a "via" element into it, including the
                                                            >> >sender.
                                                            >> >> >>
                                                            >> >> >>What's happening is that if the WM intermediaries see a "rev"
                                                            >> >> >>element in the response, they insert a "via" element into it.
                                                            >But
                                                            >> >the
                                                            >> >> >>result is an incomplete reverse path, since it lacks the
                                                            >> >endpoint's
                                                            >> >> >>URL. This might be worse than having no reverse path at all.
                                                            >> >> >>
                                                            >> >> >>What do you think?
                                                            >> >> >>
                                                            >> >> >>RC
                                                            >> >> >>
                                                            >> >> >>
                                                            >> >> >>> Cool :)
                                                            >> >> >>>
                                                            >> >> >>> There's a SOAP-RP version of the logging intermediary at
                                                            >> >> >>> http://63.202.173.234:81/log-rp.ashx
                                                            >> >> >>>
                                                            >> >> >>> Cheers
                                                            >> >> >>> Simon
                                                            >> >> >>>
                                                            >> >> >>> On Tue, 30 Oct 2001 11:31:20 -0700, in soap you wrote:
                                                            >> >> >>>
                                                            >> >> >>> >Hi Simon,
                                                            >> >> >>> >
                                                            >> >> >>> >Success! I've been able to route a request through one or
                                                            >both
                                                            >> >of
                                                            >> >> >>> >the 2 WM nodes to your endpoint. Does your intermediary
                                                            >node
                                                            >> >> >>> >support RP yet?
                                                            >> >> >>> >
                                                            >> >> >>> >Thanks,
                                                            >> >> >>> >
                                                            >> >> >>> >RC
                                                            >> >> >>> >
                                                            >> >> >>> >> Good point, I've updated it to set both the actor and
                                                            >> >mustUnderstand
                                                            >> >> >>> >> in the response.
                                                            >> >> >>> >>
                                                            >> >> >>> >> Cheers
                                                            >> >> >>> >> Simon
                                                            >> >> >>> >>
                                                            >> >> >>> >> On Tue, 30 Oct 2001 01:16:27 -0700, in soap you wrote:
                                                            >> >> >>> >>
                                                            >> >> >>> >> >Hi Simon,
                                                            >> >> >>> >> >
                                                            >> >> >>> >> >Ok, when trying to use the WM intermediary, there's a
                                                            >> >problem... it's not happy because the 4s4c SOAP-RP endpoint isn't
                                                            >> >placing an "actor" attribute on the header entry it places in the
                                                            >> >*response* message, and the WM intermediary expects to
                                                            >> >find "http://schemas.xmlsoap.org/soap/actor/next"
                                                            >> >> >>at
                                                            >> >> >>> >a minimum. You might have noticed that the WM endpoint does
                                                            >> >this with SOAP-RP headers in the response. With none specified at
                                                            >> >all, and it being aware that it's not the "default actor", the
                                                            >> >intermediary thinks that it is not the target of the header entry.
                                                            >> >It's always seemed to me that headers
                                                            >> >> >>in
                                                            >> >> >>> >response messages need to specify their target, no
                                                            >differently
                                                            >> >than those in request messages, for all the same reasons. If there
                                                            >> >are multiple intermediaries in the path, how would header entries
                                                            >in
                                                            >> >the response message get processed correctly without targeting
                                                            >them
                                                            >> >at the proper actor (which
                                                            >> >> >>> >might be associated with only one of possibly many nodes in
                                                            >> >the path)? Of course a routing header is most
                                                            >> >> >>> >> >conveniently handled by using actor "next", for obvious
                                                            >> >reasons. This issue doesn't even exist until you start using
                                                            >> >intermediaries.
                                                            >> >> >>> >> >
                                                            >> >> >>> >> >What do you think??
                                                            >> >> >>> >> >
                                                            >> >> >>> >> >Anyway, looking at the wire dumps, everything is fine,
                                                            >> >other than this.
                                                            >> >> >>> >> >
                                                            >> >> >>> >> >RC
                                                            >> >> >>> >> >
                                                            >> >> >>> >> >> Assuming you can get a connection, there's a SOAP-RP
                                                            >> >enabled version
                                                            >> >> >>> >> >> of the interop endpoint running at
                                                            >> >> >>> >> >> http://63.202.173.234:81/ilab-rp.ashx
                                                            >> >> >>> >> >>
                                                            >> >> >>> >> >> All the SOAP-RP error handling isn't in place yet, but
                                                            >> >the basics
                                                            >> >> >>> >> >> should work fine.
                                                            >> >> >>> >> >>
                                                            >> >> >>> >> >> Cheers
                                                            >> >> >>> >> >> Simon
                                                            >> >> >>> >> >>
                                                            >> >> >>> >> >> On Mon, 29 Oct 2001 09:04:21 -0800, in soap you wrote:
                                                            >> >> >>> >> >>
                                                            >> >> >>> >> >> >I have a SOAP-RP enabled version of the logger
                                                            >running
                                                            >> >at
                                                            >> >> >>> >> >> >http://63.202.173.234:81/log-rp.ashx which i've been
                                                            >> >testing in
                                                            >> >> >>> >> >> >conjunction with the White Mesa SOAP-RP enabled
                                                            >endpoint.
                                                            >> >> >>> >> >> >
                                                            >> >> >>> >> >> >I'll try and get a SOAP-RP enabled endpoint up and
                                                            >> >running as well.
                                                            >> >> >>> >> >> >
                                                            >> >> >>> >> >> >Cheers
                                                            >> >> >>> >> >> >Simon
                                                            >> >> >>> >> >> >www.pocketsoap.com
                                                            >> >> >>> >> >> >
                                                            >> >> >>> >> >> >
                                                            >> >> >>> >> >> >On Sun, 28 Oct 2001 07:16:53 -0700, in soap you wrote:
                                                            >> >> >>> >> >> >
                                                            >> >> >>> >> >> >>Hi Simon,
                                                            >> >> >>> >> >> >>
                                                            >> >> >>> >> >> >>Looks good, I'll give it a shot when I get a chance.
                                                            >A
                                                            >> >similar thing is
                                                            >> >> >>> >> >> >>available at the White Mesa site [1]. This is
                                                            >supported
                                                            >> >by the normal
                                                            >> >> >>> >> >> >>interop endpoint at
                                                            >> >http://www.whitemesa.net/interop/std.
                                                            >> >> >>> >> >> >>
                                                            >> >> >>> >> >> >>If you could be convinced to get a SOAP-RP endpoint
                                                            >> >running, interop testing
                                                            >> >> >>> >> >> >>using multiple hop routing would be possible. A SOAP-
                                                            >RP
                                                            >> >endpoint is
                                                            >> >> >>> >> >> >>available at WM also [2], with schema and WSDL
                                                            >> >definitions for the test
                                                            >> >> >>> >> >> >>service also available. Unfortunately, no other
                                                            >nodes
                                                            >> >exist at the moment
                                                            >> >> >>> >> >> >>for proper testing.
                                                            >> >> >>> >> >> >>
                                                            >> >> >>> >> >> >>You may be right about toolkits in general. The WM
                                                            >> >server, because of the
                                                            >> >> >>> >> >> >>circumstances of its origin, had to have
                                                            >intermediary
                                                            >> >support baked in early
                                                            >> >> >>> >> >> >>for gateway duties.
                                                            >> >> >>> >> >> >>
                                                            >> >> >>> >> >> >>I hope that more intermediary nodes can be brought
                                                            >up
                                                            >> >for interop testing in
                                                            >> >> >>> >> >> >>the near future. This is a very interesting area.
                                                            >> >> >>> >> >> >>
                                                            >> >> >>> >> >> >>Thanks,
                                                            >> >> >>> >> >> >>
                                                            >> >> >>> >> >> >>RC
                                                            >> >> >>> >> >> >>
                                                            >> >> >>> >> >> >>[1]
                                                            >> >http://www.whitemesa.net/std/relay/interop_relay_index.htm
                                                            >> >> >>> >> >> >>[2] http://www.whitemesa.com/wmsoapsvc_rp.htm
                                                            >> >> >>> >> >> >>
                                                            >> >> >>> >> >> >>> As an experiment in building SOAP intermediaries,
                                                            >i
                                                            >> >put together a
                                                            >> >> >>> >> >> >>> simple intermediary that does request/response
                                                            >> >logging, and a log
                                                            >> >> >>> >> >> >>> viewer.
                                                            >> >> >>> >> >> >>>
                                                            >> >> >>> >> >> >>> There's a request Header that indicates the next
                                                            >hop
                                                            >> >that the request
                                                            >> >> >>> >> >> >>> should be sent to [this should probably be moved
                                                            >to
                                                            >> >SOAP-RP], and the
                                                            >> >> >>> >> >> >>> response contains a header with the link to the
                                                            >> >viewer page for that
                                                            >> >> >>> >> >> >>> capture.
                                                            >> >> >>> >> >> >>>
                                                            >> >> >>> >> >> >>> Here's an example request/response with the
                                                            >headers
                                                            >> >populated
                                                            >> >> >>> >> >> >>> <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://schemas.pocketsoap.com/log/2001/01/'
                                                            >> >> >>> >> >> >>> 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:Log
                                                            >> >S:actor='http://schemas.pocketsoap.com/log/2001/01/'>
                                                            >> >> >>> >> >> >>> <a:NextHop>http://mayhem/ilab/soap.asp</a:NextHop>
                                                            >> >> >>> >> >> >>> </a:Log>
                                                            >> >> >>> >> >> >>> </S:Header>
                                                            >> >> >>> >> >> >>> <S:Body><d:echoString>
                                                            >> >> >>> >> >> >>> <inputString b:type='c:string'>Hello World !
                                                            >> ></inputString>
                                                            >> >> >>> >> >> >>> </d:echoString>
                                                            >> >> >>> >> >> >>> </S:Body></S:Envelope>
                                                            >> >> >>> >> >> >>>
                                                            >> >> >>> >> >> >>> <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/">
                                                            >> >> >>> >> >> >>> <sp:Header
                                                            >> >xmlns:sp="http://schemas.xmlsoap.org/soap/envelope/">
                                                            >> >> >>> >> >> >>> <lg:logResults
                                                            >> >> >>> >> >> >>>
                                                            >> >> >>> >> >>
                                                            >>
                                                            >>>>xmlns:lg="http://schemas.pocketsoap.com/log/2001/01/">http://63.202
                                                            >.
                                                            >> >173.234:
                                                            >> >> >>> >> >> >>81/logViewer.aspx?id=9550da03-bf88-425a-87bd-
                                                            >> >286e97fba9eb</lg:logResults>
                                                            >> >> >>> >> >> >>> </sp:Header>
                                                            >> >> >>> >> >> >>> <SOAP-ENV:Body>
                                                            >> >> >>> >> >> >>> <m:echoStringResponse
                                                            >> >xmlns:m="http://soapinterop.org/">
                                                            >> >> >>> >> >> >>> <outputString xsi:type="xsd:string">Hello World !
                                                            >> ></outputString>
                                                            >> >> >>> >> >> >>> </m:echoStringResponse>
                                                            >> >> >>> >> >> >>> </SOAP-ENV:Body></SOAP-ENV:Envelope>
                                                            >> >> >>> >> >> >>>
                                                            >> >> >>> >> >> >>> I'm coming to the conclusion that your average
                                                            >soap
                                                            >> >client/server
                                                            >> >> >>> >> >> >>> toolkit doesn't make a good starting point for
                                                            >> >building
                                                            >> >> >>> >> >> >>> intermediaries, what do you think ?
                                                            >> >> >>> >> >> >>>
                                                            >> >> >>> >> >> >>> The service is up and running at
                                                            >> >http://63.202.173.234:81/log.ashx if
                                                            >> >> >>> >> >> >>> anyone wants to try it out.
                                                            >> >> >>> >> >> >>>
                                                            >> >> >>> >> >> >>> Cheers
                                                            >> >> >>> >> >> >>> Simon
                                                            >> >> >>> >> >> >>> www.pocketsoap.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@y...
                                                            >> >> >>> >> >> >>>
                                                            >> >> >>> >> >> >>>
                                                            >> >> >>> >> >> >>>
                                                            >> >> >>> >> >> >>> 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
                                                            >> >> >>int
                                                            >> >> >>> >eroperability issues. Please stay on-topic.
                                                            >> >> >>> >> >> >>
                                                            >> >> >>> >> >> >>To unsubscribe from this group, send an email to:
                                                            >> >> >>> >> >> >>soapbuilders-unsubscribe@y...
                                                            >> >> >>> >> >> >>
                                                            >> >> >>> >> >> >>
                                                            >> >> >>> >> >> >>
                                                            >> >> >>> >> >> >>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 i
                                                            >> >> >>nte
                                                            >> >> >>> >roperability issues. Please stay on-topic.
                                                            >> >> >>> >> >> >
                                                            >> >> >>> >> >> >To unsubscribe from this group, send an email to:
                                                            >> >> >>> >> >> >soapbuilders-unsubscribe@y...
                                                            >> >> >>> >> >> >
                                                            >> >> >>> >> >> >
                                                            >> >> >>> >> >> >
                                                            >> >> >>> >> >> >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 in
                                                            >> >> >>ter
                                                            >> >> >>> >operability issues. Please stay on-topic.
                                                            >> >> >>> >> >>
                                                            >> >> >>> >> >> To unsubscribe from this group, send an email to:
                                                            >> >> >>> >> >> soapbuilders-unsubscribe@y...
                                                            >> >> >>> >> >>
                                                            >> >> >>> >> >>
                                                            >> >> >>> >> >>
                                                            >> >> >>> >> >> 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 inte
                                                            >> >> >>rop
                                                            >> >> >>> >erability issues. Please stay on-topic.
                                                            >> >> >>> >> >
                                                            >> >> >>> >> >To unsubscribe from this group, send an email to:
                                                            >> >> >>> >> >soapbuilders-unsubscribe@y...
                                                            >> >> >>> >> >
                                                            >> >> >>> >> >
                                                            >> >> >>> >> >
                                                            >> >> >>> >> >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 inter
                                                            >> >> >>ope
                                                            >> >> >>> >rability issues. Please stay on-topic.
                                                            >> >> >>> >>
                                                            >> >> >>> >> To unsubscribe from this group, send an email to:
                                                            >> >> >>> >> soapbuilders-unsubscribe@y...
                                                            >> >> >>> >>
                                                            >> >> >>> >>
                                                            >> >> >>> >>
                                                            >> >> >>> >> 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 http://docs.yahoo.com/info/terms/
                                                            >
                                                          Your message has been successfully submitted and would be delivered to recipients shortly.