Extra parameters
by other posts by this author
Apr 2 2001 6:45PM messages near this date
Re: Interop between MS .NET and Apache SOAP 2.1
|
Re: [soapbuilders] Extra parameters
I'm running some extra tests against Kafka, and one of the tests I
tried is sending an extra parameter, basically this request:
<S:Envelope xmlns:S='http://schemas.xmlsoap.org/soap/envelope/'
xmlns:SOAP-ENC='http://schemas.xmlsoap.org/soap/encoding/'
S:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'
xmlns:xsd='http://www.w3.org/1999/XMLSchema'
xmlns:xsi='http://www.w3.org/1999/XMLSchema-instance'>
<S:Body>
<m:echoInteger xmlns:m='http://soapinterop.org/'>
<inputInteger xsi:type='xsd:int'> 32768</inputInteger>
<dummyParam xsi:type='xsd:string'> xyz</dummyParam>
</m:echoInteger>
</S:Body>
</S:Envelope>
My stuff works, and I'm trying to decide how I feel about that. I'm
basically matching up params by name, but I'm not currently checking
to see if there are extra parameters.
So, does everyone think this should be a fault? Or is it acceptable
to ignore extraneous parameters? Preliminary tests using Simon's
pocketSOAP interop client (thanks, Simon) show mixed results among
the toolkits:
4S4C: OK
SOAP::Lite: OK
SQLData: Complained
Frontier: Complained
I had some trouble reaching any of the others right now, but I'm
guessing we'll continue to get mixed results.
Thanks,
Chris
Thread:
Paul Kulchenko
Chris Dix
|