The interesting thing is that he did not use the HTTPClient library (although using this should have allowed the Digest and NTLM authentication to work since the library supports it) because the HTTPSender class (see source here) does in fact support HTTP 1.1, just not by default. The trick is to set the right property on the web service stub so that the Axis engine does the right thing.
The other note to John's post is that you can use cfinvoke if you want to, but you just have to use cfobject/CreateObject to create the web service "stub" first, then pass that in as the webservice attribute of cfinvoke.
<cfset ws = CreateObject("webservice", "https://webservice.yourcompany.com/sql/whatever_endpoint?wsdl")>
<cfset ws._setProperty("axis.transport.version", "1.1")>
<cfinvoke webservice="ws" method="JJData" returnvariable="result">
</cfinvoke>
John also notes that processing the result set and turning it in to a query is pretty slow. Not sure what is causing this other than there is a large amount of data getting processed.
5 comments:
Hey Tom - I chose to not switch the to the Common Lib because I didn't want to mess with the default settings on the CF server. The Common library definitely worked with the SQL Server Endpoints, but I'm in an environment where I have to consume both SQL Server Endpoints and CFCs by way of web services... and I read on your previous post that the alternative HTTP lib doesn't do so well with webservice CFCs.
That's my reasoning... for what it's worth.
Another question - Is there any benefit to using the CFINVOKE tag after setting up with the CFOBJECT tag?
No problem using the default HTTP provider. If it works (and we know the default does) it works.
Nope, no difference at all using cfinvoke or function syntax, which was my point. You can code it any way you prefer - there is absolutely NO difference in functionality. Its just syntax.
When I try to access a SSL webservice it always returns this error
The fault returned when invoking the web service operation is:
AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}
Server.userException faultSubcode: faultString: java.net.ConnectException: Connection timed out:
Any suggestions would be greatly appreciated!
Hi Tom,
I'm trying to connect to Exchange Web Services and I think my issue is related to NTLM authentication. I changed my client-config.wsdd as described and I'm trying to hit our Exchange server's wsdl file, which I can pull up on a browser on the server here:
https://(ourserver).com/EWS/Services.wsdl
I'm trying to use this code, but still get 401 (unauthorized) errors.
I can get to it through the browser, though... thoughts?
Thanks for any help you can offer!
Mike
Mike,
You CFML didn't come through but I would use a TCP monitoring tool (sniffer.exe in the CF runtime/bin directory would work) to verify that the NTLM handshake is happening and I would also check the IIS logs to see why the auth (if there ) is getting rejected.
Post a Comment