Getting different architectures to talk can be a pain, even when using standards like SOAP.
In this case, the .NET WSDL imports Delphi generated WSDL in a different manner than you’d expect at first sight: when having both an ‘out’ parameter and a function ‘result’, the ‘result’ is not imported well.
But alas: SOAP didn’t accommodate for this situation in the past, and now SOAP now has some additions to solve this.
Bruneau Babet explains this here: [WayBack] SOAP inconsistency? Delphi 2010 (Win32) Server and .NET Client swapping ‘out-parameter’ and ‘result’. – Stack Overflow.
There he explains how to use the parameterOrder
attribute, which the Delphi WSDL importer and exporter still do not support.
–jeroen