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

RE: [soapbuilders] New SOAP & WSDL Server with Round 1 & 2 Interoperability Compliance

Expand Messages
  • Bob Cunnings
    Hi Kingsley, Sorry, but there is one more thing... In the schema defining the compound types, the attribute elementFormDefault has the value qualified .
    Message 1 of 6 , Nov 2, 2001
    • 0 Attachment
      Hi Kingsley,

      Sorry, but there is one more thing...

      In the schema defining the compound types, the attribute
      "elementFormDefault" has the value "qualified". This conflicts with
      the Round 2 definitions, in which the member elements of the
      compound types have unqualified names. (The default value of
      "unqualified" is in force)

      Thanks!

      RC

      >
      > Bob,
      >
      >
      > >-----Original Message-----
      > >From: Bob Cunnings [mailto:cunnings@...]
      > >Sent: Thursday, November 01, 2001 7:10 PM
      > >To: soapbuilders@yahoogroups.com
      > >Subject: Re: [soapbuilders] New SOAP & WSDL Server with Round
      > >1 & 2 Interoperability Compliance
      > >
      > >
      > >Hi Kingsley,
      > >
      > >Looks good, we're always happy to see another endpoint. However, to
      > >come into compliance with the Round 2 interop requirements [1], the
      > >following need to be adjusted:
      > >
      > >Schema targetNamespace: needs to be "http://soapinterop.org/xsd" for
      > >the compound types used in interop testing.
      >
      > OK.
      >
      > >Method namespace: needs to be "http://soapinterop.org/" (in binding,
      > >soap:body "namespace" attribute).
      > >SOAPAction URI: needs to be "http://soapinterop.org/" (in
      > >binding,soap:operation "soapAction" attribute).
      > >
      > >Of course this need apply only to the operations defined by
      > >the Round 2
      > >specs. The specifications and reference WSDL docs are found at:
      > >
      > >http://www.whitemesa.com/interop.htm
      > >
      >
      > OK.
      >
      > Will be fixed ASAP.
      >
      > Kingsley
      > >Thanks,
      > >
      > >RC
      > >
      > >
      > >
      > >> All,
      > >>
      > >> I would like bring the following SOAP/WSDL endpoint to your
      > >attention:
      > >>
      > >> http://demo.openlinksw.com:8890/SOAP/services.wsdl
      > >>
      > >>
      > >> Virtuoso is our muli-protocol eBusiness server that includes support
      > >> for:
      > >> SOAP, WSDL, UDDI, XQUERY, XSL-T, SQL, ODBC and many other related
      > >> standards.
      > >>
      > >> Please e-mail any queries feedback re. The above to:
      > >> mailto:soap@...
      > >>
      > >> Regards,
      > >> Kingsley Idehen
      > >> OpenLink Software
      > >>
      > >>
      > >>
      > >>
      > >>
      > >>
      > >>
      > >>
      > >> -----------------------------------------------------------------
      > >> 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 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/
      >
    • Kingsley Idehen
      Bob, OK. Kingsley
      Message 2 of 6 , Nov 2, 2001
      • 0 Attachment
        Bob,

        OK.

        Kingsley

        >-----Original Message-----
        >From: Bob Cunnings [mailto:cunnings@...]
        >Sent: Friday, November 02, 2001 11:21 AM
        >To: soapbuilders@yahoogroups.com
        >Subject: RE: [soapbuilders] New SOAP & WSDL Server with Round
        >1 & 2 Interoperability Compliance
        >
        >
        >Hi Kingsley,
        >
        >Sorry, but there is one more thing...
        >
        >In the schema defining the compound types, the attribute
        >"elementFormDefault" has the value "qualified". This conflicts with
        >the Round 2 definitions, in which the member elements of the
        >compound types have unqualified names. (The default value of
        >"unqualified" is in force)
        >
        >Thanks!
        >
        >RC
        >
        >>
        >> Bob,
        >>
        >>
        >> >-----Original Message-----
        >> >From: Bob Cunnings [mailto:cunnings@...]
        >> >Sent: Thursday, November 01, 2001 7:10 PM
        >> >To: soapbuilders@yahoogroups.com
        >> >Subject: Re: [soapbuilders] New SOAP & WSDL Server with Round
        >> >1 & 2 Interoperability Compliance
        >> >
        >> >
        >> >Hi Kingsley,
        >> >
        >> >Looks good, we're always happy to see another endpoint. However, to
        >> >come into compliance with the Round 2 interop requirements [1], the
        >> >following need to be adjusted:
        >> >
        >> >Schema targetNamespace: needs to be "http://soapinterop.org/xsd" for
        >> >the compound types used in interop testing.
        >>
        >> OK.
        >>
        >> >Method namespace: needs to be "http://soapinterop.org/" (in binding,
        >> >soap:body "namespace" attribute).
        >> >SOAPAction URI: needs to be "http://soapinterop.org/" (in
        >> >binding,soap:operation "soapAction" attribute).
        >> >
        >> >Of course this need apply only to the operations defined by
        >> >the Round 2
        >> >specs. The specifications and reference WSDL docs are found at:
        >> >
        >> >http://www.whitemesa.com/interop.htm
        >> >
        >>
        >> OK.
        >>
        >> Will be fixed ASAP.
        >>
        >> Kingsley
        >> >Thanks,
        >> >
        >> >RC
        >> >
        >> >
        >> >
        >> >> All,
        >> >>
        >> >> I would like bring the following SOAP/WSDL endpoint to your
        >> >attention:
        >> >>
        >> >> http://demo.openlinksw.com:8890/SOAP/services.wsdl
        >> >>
        >> >>
        >> >> Virtuoso is our muli-protocol eBusiness server that includes
        >> >> support
        >> >> for:
        >> >> SOAP, WSDL, UDDI, XQUERY, XSL-T, SQL, ODBC and many other related
        >> >> standards.
        >> >>
        >> >> Please e-mail any queries feedback re. The above to:
        >> >> mailto:soap@...
        >> >>
        >> >> Regards,
        >> >> Kingsley Idehen
        >> >> OpenLink Software
        >> >>
        >> >>
        >> >>
        >> >>
        >> >>
        >> >>
        >> >>
        >> >>
        >> >> -----------------------------------------------------------------
        >> >> 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 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/
        >
        >
        >
      Your message has been successfully submitted and would be delivered to recipients shortly.