when creating a request with named parameters realbasic seems a
little lazy in it's creation of the soap envelope. A request with
other clients (like using the apple cocoa methods or some java tools
creates a method request like
<SOAP-ENV:Body>
-
<m:authenticate xmlns:m="http://beans.ventus.com";>
-
<u xsi:type="xsd:string">
bobbarker
</u>
-
<p xsi:type="xsd:string">
s4rgKz0R0r97GwJBjZ6DSwiAYJw=
</p>
</m:authenticate>
</SOAP-ENV:Body>
where realbasic's envelope for the same request looks like
<authenticate xmlns="http/beans.ventus.com"><u
xsi:type="xsd:string">bobbarker</u><p
xsi:type="xsd:string">s4rgKz0R0r97GwJBjZ6DSwiAYJw=</p><a
xsi:type="xsd:string"></a></authenticate></SOAP:Body>
note the missing linking of the xmlns to the named params
m:authenticate and xmlns:m=
now a java client adds the namespace reference to each named param as
well so you get m:u and m:p
my belief is that you are working to the spec, but by adding this
namespace linking you will get better interop with other SOAP server
implementations like the AXIS implementation for one that will not
understand your calls as being named parameters and will instead fall
back to ordering.
Does any one have any ideas on the cleanest way to work around this?
(I have posted a report the the feedback system as well < http://
www.realsoftware.com/feedback/viewreport.php?reportid=wobuxezt>
Thanks
Sam D
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
