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

RE: [soapbuilders] another question re: round B

Expand Messages
  • graham glass
    Messagethanks! we ll use the rich endpoint when testing interop for these additional data types. please post the address of the new round B endpoint when it is
    Message 1 of 27 , Jul 31, 2001
    • 0 Attachment
      Message
      thanks! we'll use the rich endpoint when testing interop
      for these additional data types.
       
      please post the address of the new round B endpoint when it is live.
       
      cheers,
      graham
      -----Original Message-----
      From: Jonathan Hawkins [mailto:jhawk@...]
      Sent: Tuesday, July 31, 2001 5:49 PM
      To: soapbuilders@yahoogroups.com
      Cc: Vineel Gattu; Keith Ballinger
      Subject: RE: [soapbuilders] another question re: round B

      Hi Graham

       

      We put up the endpoint with all the types since this was discussed at N+I in Vegas.

      We will put an endpoint with just the round b types.

       

      -jhawk

       

      -----Original Message-----
      From: graham glass [mailto:graham-glass@...]
      Sent: Tuesday, July 31, 2001 2:58 PM
      To: soapbuilders@yahoogroups.com
      Subject: RE: [soapbuilders] another question re: round B

       

      hi keith,

       

       

       

      cheers,

      graham

      -----Original Message-----
      From: Keith Ballinger [mailto:keithba@...]
      Sent: Tuesday, July 31, 2001 4:20 PM
      To: soapbuilders@yahoogroups.com
      Subject: RE: [soapbuilders] another question re: round B

      I assumed you met ASP.NET Web Services (asmx), but I don't see these. Do you mean the remoting endpoints?

      -----Original Message-----
      From: graham glass [mailto:graham-glass@...]
      Sent: Tuesday, July 31, 2001 3:17 AM
      To: soapbuilders@yahoogroups.com
      Subject: [soapbuilders] another question re: round B

      hi guys,

      are the types xsd:duration, time and date part of round B interop?

      the MS .NET wsdl defines these types, which is causing GLUE to
      generate exceptions because it doesn't understand these types yet.
      IMHO if these types are not part of the interop, it would be good if
      the test WSDL files did not include references to these types.

      cheers,
      graham


      -----------------------------------------------------------------
      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.



      -----------------------------------------------------------------
      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.



      -----------------------------------------------------------------
      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.




      -----------------------------------------------------------------
      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.
    Your message has been successfully submitted and would be delivered to recipients shortly.