17(fwd) Re: [soapbuilders] WSDL and method names
- Jan 31, 2001Dave,
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 correct ? i.e. Manila
expects a SOAP request similar to
On Wed, 31 Jan 2001 06:29:02 -0800 (PST), in soap Paul Kulchenko
>--- 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,
>> 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
>> 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.
> STag ::= '<' Name (S Attribute)* S? '>'
>  Name ::= (Letter | '_' | ':') (NameChar)*
> Letter ::= BaseChar | Ideographic
>  NameChar ::= Letter | Digit | '.' | '-' | '_' | ':' |
>CombiningChar | Extender
> BaseChar ::= [#x0041-#x005A] | [#x0061-#x007A] | .....
>So, as I understand there is no place for '/'.
>Best wishes, Paul.