Woohoo!
That did it.
Right. The SOAP generated by the Tersus SOAP model is causing an error in he (.Net) webservice on these 2 counts:
> Tersus uses "soapenv" tags instead of plain "soap" tags
> Tersus translates booleans to y/n characters. .Net's proxy classes seem unable to translate anything but "true" and "false" strings into typed booleans, so fail to parse the Tersus request.
Posting using Tersus HTTP Post (inside a "Service" block), with "soap" tags in place of "soapenv" and "true"/"false" in place of "y"/"n" results in a successful execution of the webservice!
Would it be possible to add a .Net SOAP to cope with MS.Net's SOAP preferences?
Ralph
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign
