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

25RE: [soapbuilders] Interoperability lab

Expand Messages
  • Tony Hong
    Feb 1, 2001
    • 0 Attachment
      Hi Sanjiva,
       
      OK, gotcha. Per Simon's previous note, MS Toolkit is limited to simple types. I'll look around for an alternative
      example, and if I can't find one, I try and set one up with .NET B1 or something like that.
       
      Cheers,
      Tony
       
       -----Original Message-----
      From: Sanjiva Weerawarana [mailto:sanjiva@...]
      Sent: Thursday, February 01, 2001 4:12 AM
      To: soapbuilders@yahoogroups.com
      Subject: RE: [soapbuilders] Interoperability lab


      Hi Tony,

      What I'm actually looking for is a service that doesn't put in the xsi:type
      stuff and relies on WSDL/SDL/whatever to get the knowledge of the types of
      parameters of a call. We recently put in support in Apache SOAP to handle
      that and I haven't been able to find any complex type tests. I wrote a
      simpel test to talk to your guidgen server (written in MS SOAP I believe)
      and it works fine.

      Sanjiva.

      "Tony Hong" <thong@...> on 01/31/2001 08:17:32 PM

      Please respond to soapbuilders@yahoogroups.com

      To:   <soapbuilders@yahoogroups.com>
      cc:
      Subject:  RE: [soapbuilders] Interoperability lab




      Sanjiva,

      One  other note -  to illustrate the existing struct array test, here is
      the  request/response wiredump. In
      this  example, it's a Apache 2.0 client hitting a SOAPLite server (it works
      successfully) . Let me know if
      this  is what you're thinking about, or if you need something different.
      Thanks

      Tony

      ----------- Apache Requst  -----------------------

      POST  /perl/soaplite.cgi HTTP/1.0
      Host: tony:8080
      Content-Type:  text/xml
      Content- Length: 541
      SOAPAction:  "urn:xmethodsInterop#echoStruct"

      <SOAP-ENV:Envelope  xmlns:SOAP-ENV="
      http://schemas.xmlsoap.org/soap/envelope/"  xmlns:xsi="
      http://www.w3.org/1999/XMLSchema-instance"  xmlns:xsd="
      http://www.w3.org/1999/XMLSchema">
      <SOAP-ENV:Body>
      <ns1:echoStruct  xmlns:ns1="urn:xmethodsInterop"  SOAP-ENV:encodingStyle="
      http://schemas.xmlsoap.org/soap/encoding/">
      <echo  xsi:type="ns1:SOAPStruct">
      <varInt  xsi:type="xsd:int">3</varInt>
      <varFloat  xsi:type="xsd:float">1.2</varFloat>
      <varString  xsi:type="xsd:string">Hello</varString>
      </echo>
      </ns1:echoStruct>
      </SOAP-ENV:Body>
      </SOAP-ENV:Envelope>

      ------------- SOAPLite  response --------------------------

      HTTP/1.1 200 OK
      Content- Length:  672
      Content-Type: text/xml
      glue-routing: true
      date: Thu, 01 Feb 2001  01:11:21 GMT
      server: Apache/1.3.14 (Unix) PHP/4.0.1pl2
      soapserver:  SOAP::Lite/Perl/0.45

      <?xml version="1.0"  encoding="UTF-8"?><SOAP-ENV:Envelope  xmlns:SOAP-ENC="
      http://schemas.xmlsoap.org/soap/encoding/"  SOAP-ENV:encodingStyle="
      http://schemas.xmlsoap.org/soap/encoding/"  xmlns:xsi="
      http://www.w3.org/1999/XMLSchema-instance"  xmlns:SOAP-ENV="
      http://schemas.xmlsoap.org/soap/envelope/"  xmlns:xsd="
      http://www.w3.org/1999/XMLSchema">
      <SOAP-ENV:Body>
      <namesp1:echoStructResponse  xmlns:namesp1="urn:xmethodsInterop">
      <SOAPStruct  xsi:type="namesp1:SOAPStruct">
      <varFloat  xsi:type="xsd:float">1.2</varFloat>
      <varString  xsi:type="xsd:string">Hello</varString>
      <varInt  xsi:type="xsd:int">3</varInt>
      </SOAPStruct>
      </namesp1:echoStructResponse>
      </SOAP-ENV:Body>
      </SOAP-ENV:Envelope>

      -----Original Message-----
      From: Tony  Hong [mailto:thong@...]
      Sent: Wednesday, January 31, 2001  4:57 PM
      To: soapbuilders@yahoogroups.com
      Subject: RE:  [soapbuilders] Interoperability lab


      Hi  Sanjiva,

      Thanks, I'm glad you find the idea  useful!

      The  yahoo group is listed now - I accidently delisted it from their
      directory, but  it's
      visible again. Just search for"soapbuilders"  at groups.yahoo.com and you
      should
      see  it pop up .

      The  testbed as I'vedescribed has an "echoStruct" and "echoStructArray"
      methods -
      I've built this service already for  Apache and SOAP::Lite - for Apache,
      the service uses
      the  Bean serializer to map to/from a simple object. See

      http://www.xmethods.net/detail.html?id=10  for SOAP::Lite
      and
      http://www.xmethods.net/detail.html?id=11   for Apache

      Is  this what you are thinking of?

      As  far as MS or 4s4c, I'm not sure of any other existing services that
      involve
      complex types - Simon, do you know of  any?

      If  you describe the kind of type/structure you'd like to see built as an
      "echo"  , I can make sure its part
      of  the target test set and start the construction in a variety of
      implementations, including the ones
      you  mention.

      Cheers,
      Tony


      -----Original Message-----
      From: Sanjiva Weerawarana  [mailto:sanjiva@...]
      Sent: Wednesday, January 31, 2001 9:42  AM
      To: soapbuilders@yahoogroups.com
      Subject: Re:  [soapbuilders] Interoperability lab


      Hi  Tony,

      I think this is a great idea! Thanks for starting the  work!

      Do u know of a service implemented with MS SOAP, 4S4C, ... etc.  that uses
      complex types and is available on the net? I'm trying to test  the apache
      soap interoperabilty using complex types with non-Apache SOAP  services and
      I can't seem to find interesting services to  try.

      Also, what's the Yahoo group for this? I can't seem to find the  group to
      change my email  address!

      Bye,

      Sanjiva.

      Jacek Kopecky  <jacek@...> on 01/31/2001 10:23:07 AM

      Please respond to  soapbuilders@yahoogroups.com

      To:   Soapbuilders  <soapbuilders@yahoogroups.com>
      cc:
      Subject:  Re:  [soapbuilders] Interoperability lab



      I'd add a circular  structure:

      LinkedList echoLinkedList(LinkedList  linkedList)

      where the definition in Java would be

      public class  LinkedList {
          int x;
          LinkedList  next;
      }

      which means nullable and referenced next part. Sending a  circular list
      through might also help.  8-)

                                   Jacek  Kopecky
                                      Idoox



      On Wed, 31 Jan 2001, Tony Hong wrote:

      > Hi  all
      >
      > I've mentioned to a couple of you that I'm going to  create
      > an interoperability testbed. I'd like to get some  feedback
      > from this group.
      >
      > For each if a number of  different SOAP implemenation, I'm
      > planning to host a service that  exposes these methods
      >
      > String echoString(String  inputString)
      > String[] echoStringArrray(String[]  inputStringArray)
      > Integer echoInteger(Integer inputInteger)
      >  Integer[] echoIntegerArray(Integer[] inputIntegerArray)
      > Float  echoFloat(Float inputFloat)
      > Float[] echoFloatArray(Float[]  inputFloatArray)
      > SOAPStruct echoStruct( SOAPStruct  inputStruct)
      > SOAPStruct[] echoStructArray (SOAPStruct[]  inputStructArray)
      >
      > Where SOAPStruct is a simple structure  with integer, float, and
      > string fields.
      >
      > Other  possibilities include:
      > Hashmap / Associative array , using the  encoding proposed by
      > the Apache folks.
      > XML  Documents
      >
      > This "echo" service does nothing really useful  except
      > illustrate the ability of the service to accept a  clients
      > envelope, deserialize the types correctly, and then
      >  reserialize the respones into something that the client
      > can see if  it understands.
      >
      > I built this service for Apache 2.0 and  SOAP::Lite a few
      > months ago, and I think Paul Kulchenko will agree  that
      > it's been really useful for testing interop  issues.
      >
      >
      > In addition to exposing these services, I  also plan to:
      >
      > * Publish wiredumps of the request and  response envelopes
      > that each implementation uses - ie, each  implementations
      > client
      > * For those implementations that  dynamically generate
      > WSDL, I will publish the WSDL generated for  each of these
      > methods.
      >
      > I think this is a first step  to REALLY filling out those issues
      > lists for SOAP and WSDL  interoperability. It's much easier to
      > see the issues when all this  info is right in front of you.
      >
      > My question here is
      >
      > Does this set of types/methods make sense? Would you  modify
      > this list in any way?
      >
      > Thanks for any  feedback!
      >
      > Tony
      >
      >  ----------------------------------------
      > XMethods Web Services  Listings
      > http://www.xmethods.net
      >
      >
      >  To unsubscribe from this group, send an email to:
      >  soapbuilders-unsubscribe@yahoogroups.com
      >
      >
      >



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








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




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



                                                                                 
                                      Yahoo! Groups Sponsor                      
                                                                                 
                                                                                 
                                                                                 
                                                                                 
                                                              [IMAGE]            
                     [IMAGE]                                                     
                                                                                 
                                                                                 
                                                                !                
                                        www. .com                                
                                                                                 
                                                                                 
                                                                                 
                [IMAGE]                                                          
                                                                                 


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








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


    • Show all 18 messages in this topic