Thanks David.
My newbie mistake there.
Still having some issues though (HTTP:500). The webservice does work from .Net, PHP and Java. The only things I can see are differences in the SOAP message from that generated elsewhere:
instead of this (as generated for .Net web references):
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
Tersus generates:
I'm not certain, but this could be causing the HTTP:500 error.
The only other potential issue I can see is that in a successfully tested example, using an HTTP POST of the SOAP to the webservice, the booleans are represented as "true"/"false" rather than "Y"/"N" from Tersus.
Any ideas?
Thanks in advance.
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