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

Re: [soapbuilders] SOAP Builders Round III - Web Servi ces Interoperability Testing 2/27-28 2002

Expand Messages
  • Sanjiva Weerawarana
    Hi Dirk, I would like to attend this interop session. Bye, Sanjiva. ... From: Dirk_Hamstra To: Sent:
    Message 1 of 1 , Jan 27, 2002
    • 0 Attachment
      Hi Dirk,

      I would like to attend this interop session.



      ----- Original Message -----
      From: "Dirk_Hamstra" <dirk.hamstra@...>
      To: <soapbuilders@yahoogroups.com>
      Sent: Thursday, January 17, 2002 3:24 AM
      Subject: [soapbuilders] SOAP Builders Round III - Web Services
      Interoperability Testing 2/27-28 2002

      What? SOAP Builders Round III - Web Services Interoperability
      When? 27-28 February 2002
      Where? IONA's Waltham Offices -

      It's been a long time since the last face-to-face meeting.
      SOAPBuilders has started working on WSDL interop in earnest and
      seeing as many participants have tests ready, we thought this was a
      good time to call a F2F. IONA will co-host the event with Microsoft
      at their Waltham, MA offices.

      The overall agenda starts with a hosted dinner for whoever's in
      on the night of the 26th, followed by a day of testing core WSDL
      features and a common scenario on the 27th. After a hard day of
      interop we will get together again for Dinner in Boston. Day two will
      answer unresolved questions from day one and tackle more complex WSDL
      interop issues.

      The proposed overall testing strategy is to make sure that SOAP/WSDL
      tools can:
      -generate wsdl's for given scenarios correctly and consume
      generated by others
      -consume and reuse given wsdl's

      We will propose a detailed plan in the next few days, but we are
      considering the following areas that were referenced most actively on
      soapbuilders/wsdl lists lately:

      -wsdl:import, schema import scenarios.
      Rationale: Import is a critical mechanism that enables clear wsdl
      authoring and services versioning/decomposition. There were several
      spec interpretation issues raised on soapbuilders list (see thread
      [1] for example) that need to be cleared through careful interop

      -document/literal services with multiple schemas.
      Rationale: operations with document/literal style are critical for
      complex XML data exchange. There were many discussions on the list
      around wire representation of document/literal messages, especially
      with the use of xml types from several namespaces.

      -miscellaneous ad hoc testing generated by known interop issues in
      SOAP binding: wsdl referential integrity, overloaded methods.
      Rationale: while soap interop testing effort matures, these local
      WSDL Interop problems occur every now and then (see threads [2-3],
      for example). While the agreement on their solution/spec
      interpretation is reached a while ago, the only way to nail them is
      to address them in our regular online testing. Draft scenarios can be
      created on this f2f.

      Book your flights, bring your laptop/server and a wireless card (a
      WiFi WAP and wired taps to the Internet will be available for the
      event) and let Dirk know you're participating by sending him an email
      (mailto: dirk.hamstra@...)

      See you there

      Dirk Hamstra, IONA
      Philip DesAutels, Microsoft

      [1] http://groups.yahoo.com/group/soapbuilders/message/5638
      [2] http://groups.yahoo.com/group/soapbuilders/message/5082
      [3] http://groups.yahoo.com/group/soapbuilders/message/5078

      Yahoo! Groups Sponsor

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

      To unsubscribe from this group, send an email to:

      Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
    Your message has been successfully submitted and would be delivered to recipients shortly.