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

Re: [wsdl] WSDL Issue

Expand Messages
  • Simon Fell
    ... yup. ... on further examination the operations look wrong as well, the targetNamespace for the root wsdl is http://namespaces.snowboard-info.com but in the
    Message 1 of 4 , May 26, 2001
      On Sat, 26 May 2001 15:33:33 -0500, in wsdl you wrote:

      >I think u r correct. shouldn't esxsd be equal to the targetNamespace of the
      >schema?

      yup.

      >Otherwise the element is defined outside the scope of the schema???????

      on further examination the operations look wrong as well, the
      targetNamespace for the root wsdl is
      http://namespaces.snowboard-info.com
      but in the portType, the messages are refered to as
      es:GetEndorsingBoarderRequest, but es is defined as
      http://www.snowboard-info.com/EndorsementSearch.wsdl

      >> -----Original Message-----
      >> From: Simon Fell [mailto:soap@...]
      >> Sent: Saturday, May 26, 2001 3:24 PM
      >> To: wsdl@yahoogroups.com
      >> Subject: Re: [wsdl] WSDL Issue
      >>
      >>
      >> I'm not sure it is correct, looking at the first WSDL in that page, it
      >> defines new types in the http://namespaces.snowboard-info.com
      >> namespace, but in the messages section, they to via
      >> esxsd:GetEndorsingBoarder where esxsd is
      >> http://schemas.snowboard-info.com/EndorsementSearch.xsd
      >>
      >> or did i miss something ?
      >>
      >> Cheers
      >> Simon
      >>
      >>
      >> On Sat, 26 May 2001 14:52:41 -0500, in wsdl you wrote:
      >>
      >> >I ran across this example at
      >> >http://www.w3.org/2001/03/14-annotated-WSDL-examples
      >> >
      >> >The example is correct but does emphasize a concern.
      >> >
      >> >1) when a part is typed "element" and referenced to schema
      >> >2) and the binding's soap:body "namespace" attribute is used
      >> >
      >> >Spec reads Section 3.5
      >> >...although the namespace attribute only applies to content
      >> not explicitly
      >> >defined by the abstract types. ...
      >> >
      >> >A case becomes present where the namespace attribute can be
      >> declared and the
      >> >element's namespace *is* explicitly declared by the
      >> targetNamespace of the
      >> >schema (assuming XSD) which is the namespace to be used and
      >> *NOT* the text
      >> >of the soap:body namespace attribute. However, if the
      >> schema was non-XSD
      >> >*and* no targetNamespace (or such) could be isolated, the
      >> value of the
      >> >namespace would default to the "namespace" attribute.
      >> >
      >> >This seems confusing and it would seem in the interests of
      >> best practices to
      >> >either
      >> >1) declare the namespace attribute of the soap:body element
      >> equal to the
      >> >intended namespace
      >> >or
      >> >2) omit the namespace attribute *if* the element is
      >> explictly declared in
      >> >schema.
      >> >
      >> >(I would think (1) would clear any garbled confusion in either case).
      >> >
      >> >Thoughts!
      >> >
      >> >-Matt
      >> >
      >> >
      >> >
      >> >
      >> >
      >> >
      >> >
      >> >
      >> >To unsubscribe from this group, send an email to:
      >> >wsdl-unsubscribe@yahoogroups.com
      >> >
      >> >
      >> >
      >> >Your use of Yahoo! Groups is subject to
      >http://docs.yahoo.com/info/terms/
      >>
      >
      >
      >To unsubscribe from this group, send an email to:
      >wsdl-unsubscribe@yahoogroups.com
      >
      >
      >
      >Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
      >
      >
      >To unsubscribe from this group, send an email to:
      >wsdl-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.