Parms positional but not named?

[Lyndon]

It seems the parameters in method calls are positional and the names
are ignored.

For example the following is ok;

<SOAP-ENV:Body>
<ns0:doSpellingSuggestion>
<key xsi:type="xsd:string">MYKEY</key>
<phrase xsi:type="xsd:string">xwe</phrase>
</ns0:doSpellingSuggestion>
</SOAP-ENV:Body>

But this;

<SOAP-ENV:Body>
<ns0:doSpellingSuggestion>
<phrase xsi:type="xsd:string">xwe</phrase>
<key xsi:type="xsd:string">MYKEY</key>
</ns0:doSpellingSuggestion>
</SOAP-ENV:Body>

Would respond with an error like 'invalid key xwe'.

Perhaps this is related to the soap server being used ( tomcat/axis? )
rather than the code google has written?

[Google Web APIs Team]

Thanks for your comment, Lyndon.

sam...@ozemail.com.au (Lyndon) wrote in message news:<14def24b.02060...@posting.google.com>...

> It seems the parameters in method calls are positional and the names
> are ignored.

Yes, this is correct, and it's a somewhat surprising aspect of the
current Google Web API implementation that is a side effect of the
server implementation we are using (based on Apache SOAP). In our
understanding of SOAP it is legal for a service to require arguments
specified in only one order, so we believe this behavior is not
incorrect. It is quite surprising though!

Has this been a practical problem, or simply something odd?

[Lyndon]

api-s...@google.com (Google Web APIs Team) wrote in message news:<4e82c7f0.02060...@posting.google.com>...

Thanks for your reply.

Its not really a problem, I only mentioned it because the route the
data goes through ( tibco/IM ) before it ends up as SOAP XML makes it
a little more complicated to order the output elements.

Interesting though :-)