🚀 go-pugleaf

Hello Matthew,

Can you post some additional information about the WebService? I know of
couple of issues that will cause problems. They are related to namespaces.
Basically, the support in CBuilder6 for document|literal services [default
for .NET WebServices] was rudimentary. If the service, for example, uses an
unqualified element, CBuilder6 always assumed qualified element. The net
result is that the XML sent to the service would not match what was
described in the WSDL, and the service will be unable to deserialize the
data.

If you control the WebService, you can maximize compatibility with CBuilder6
by using an Rpc style service. However, if you don't control the WebService
side, then we would need to find out a little more before coming up with a
solution/workaround.

If you can post (or email me if it contains sensitive data) the WSDL, we can
diagnose the problem a little more. Alternatively, .NET Webservices are
typically good at showing a sample of the XML they expect. You can compare
that with the one CBuilder6 is generating (you can peek at the XML by
handling the OnBeforeExecute event on the THTTPRIO) and often the issue will
be evident.

There were also some issues with cases where the method or parameters were
renamed (say because they conflict with a C++ keyword)...in these cases
C++Builder6 did not always renamed the identifier properly in the XML. Again
the WSDL will reveal if that's the issue.

Cheers,

Bruneau.