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

RE: [soapbuilders] Round 3 WSDL issue

Expand Messages
  • Matt Long
    You can play the same game with the namespace on the message attribute value QName for , within the imported portType. ...
    Message 1 of 4 , Jan 30, 2002
    • 0 Attachment
      You can play the same game with the namespace on the 'message' attribute
      value QName for <input>,<output> within the imported portType.


      > -----Original Message-----
      > From: Simon Fell [mailto:soap@...]
      > Sent: Wednesday, January 30, 2002 11:53 PM
      > To: soapbuilders@yahoogroups.com
      > Subject: Re: [soapbuilders] Round 3 WSDL issue
      >
      >
      > Aren't the operations names simply scoped by the type QName on the
      > binding element ?, i.e. the binding is for a specific portType,
      > identified by its QName, so operation names only need localname
      > matches within that scope.
      >
      > Cheers
      > Simon
      >
      >
      > On Wed, 30 Jan 2002 22:35:12 -0700, in soap you wrote:
      >
      > >Hi,
      > >
      > >While looking at some of the Round 3 WSDL , I was reminded
      > that when a portType is imported whose namespace differs from
      > the targetNamespace of the importing doc, a question arises.
      > For example, Import1.wsdl [1], with targetNamespace
      > "http://soapinterop.org/" imports the portType
      > "SoapInteropImport1PortType" in namespace
      > "http://soapinterop.org/definitions/" from doc Import1b.wsdl
      > [2]. The question is: Since the operation "echoString"
      > defined in the <portType> does not match the operation
      > "echoString" defined in the <binding>
      > "SoapInteropImport1Binding" on a qname comparison basis
      > (different namespaces), does this conflict with the spec: [3]
      > >
      > >"An operation element within a binding specifies binding information
      > >for the operation with the same name within the binding's portType."
      > >
      > >Do they mean "localname" or "qname"? I think localname,
      > otherwise a binding couldn't reference a portType in another
      > namespace. Maybe I'm missing something here.
      > >
      > >Comments?
      > >
      > >RC
      > >
      > >[1] http://www.whitemesa.com/r3/import1.wsdl
      > >[2] http://www.whitemesa.com/r3/imported/import1B.wsdl
      > >[3] http://www.w3.org/TR/wsdl#_bindings
      > >
      > >
      > >
      > >
      > >-----------------------------------------------------------------
      > >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/
    Your message has been successfully submitted and would be delivered to recipients shortly.