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

17(fwd) Re: [soapbuilders] WSDL and method names

Expand Messages
  • Simon Fell
    Jan 31, 2001
    • 0 Attachment
      Dave,

      I took my findings on writing a WSDL file for Manila to the
      soapbuilders list (we were discussing WSDL inter-op), and Paul pointed
      out that /'s in element names don't appear to be valid XML. Is my
      interpretation of the Manila SOAP spec[1] correct ? i.e. Manila
      expects a SOAP request similar to

      <S:Envelope ...>
      <S:Body>
      <css/get>
      <username>...</username>
      <password>...</password>
      <siteName>...</siteName>
      </css/get>
      </S:Body>
      </S:Envelope>

      Cheers
      Simon
      [1]http://www.xml-rpc.com/manilaRpcSpec#callingManilaRpcHandlersUsingSoap


      On Wed, 31 Jan 2001 06:29:02 -0800 (PST), in soap Paul Kulchenko
      <paulclinger@...> wrote:

      >Hi, Simon!
      >
      >--- Simon Fell <soap@...> wrote:
      >> couple of separate issues here
      >> 1. There is no reason why a soap request of <css/get>...</css/get>
      >> needs to be mapped directly to a language method of css/get,
      >> different
      >> languages have different rules on legal names, and they are going
      >> to have to escape them in a manner that works for that language.
      >True, but if other implementation expect to get css/get there is no
      >way for client to alter this name on wire.
      >
      >> 2. I had no trouble generating and parsing a SOAP message using
      >> that
      >> format, but i just had a quick look through the XML spec and i'm
      >> not sure if it is a valid element name or not.
      >[40] STag ::= '<' Name (S Attribute)* S? '>'
      > [5] Name ::= (Letter | '_' | ':') (NameChar)*
      >[84] Letter ::= BaseChar | Ideographic
      > [4] NameChar ::= Letter | Digit | '.' | '-' | '_' | ':' |
      >CombiningChar | Extender
      >[85] BaseChar ::= [#x0041-#x005A] | [#x0061-#x007A] | .....
      >
      >So, as I understand there is no place for '/'.
      >
      >Best wishes, Paul.